8000 Define missing definitions for variables (#775) · unicode-org/message-format-wg@6db127f · GitHub
[go: up one dir, main page]

Skip to content

Commit 6db127f

Browse files
authored
Define missing definitions for variables (#775)
* Define missing definitions for variables During publication of v45, I found that we were missing a number of terms that we actively use in the specification. Among these are: - variable - external variable - local variable This PR defines those terms. * Update spec/syntax.md * Address comments Responding to @catamorphism's comment. This change adopts the already-problematic phrase "resolved value", which is begging for us to define it.
1 parent d3a59da commit 6db127f

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

spec/syntax.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -97,6 +97,15 @@ Attempting to parse a _message_ that is not _valid_ will result in a _Data Model
9797

9898
A **_<dfn>message</dfn>_** is the complete template for a specific message formatting request.
9999

100+
A **_<dfn>variable</dfn>_** is a _name_ associated to a resolved value.
101+
102+
An **_<dfn>external variable</dfn>_** is a _variable_
103+
whose _name_ and initial value are supplied by the caller
104+
to MessageFormat or available in the _formatting context_.
105+
Only an _external variable_ can appear as an _operand_ in an _input declaration_.
106+
107+
A **_<dfn>local variable</dfn>_** is a _variable_ created as the result of a _local declaration_.
108+
100109
> [!NOTE]
101110
> This syntax is designed to be embeddable into many different programming languages and formats.
102111
> As such, it avoids constructs, such as character escapes, that are specific to any given file

0 commit comments

Comments
 (0)
0