aboutsummaryrefslogtreecommitdiff
path: root/spec/token.md
diff options
context:
space:
mode:
authorMarshall Lochbaum <mwlochbaum@gmail.com>2020-07-18 18:26:52 -0400
committerMarshall Lochbaum <mwlochbaum@gmail.com>2020-07-18 18:29:59 -0400
commit229e2cd2f5c78b13c483a8559dead2c8f31d8e42 (patch)
tree9d6a1ff0100bda7632948987352b3d6614c3eeb5 /spec/token.md
parent010b97c8cf346dfeafc289ae66f77e8c61cd9865 (diff)
Terminology changes: subject, 1/2-modifier, Box/Unbox to Enclose/Merge, blocks
Diffstat (limited to 'spec/token.md')
-rw-r--r--spec/token.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/spec/token.md b/spec/token.md
index 8315c9c2..3c2235eb 100644
--- a/spec/token.md
+++ b/spec/token.md
@@ -6,7 +6,7 @@ A BQN *character literal* consists of a single character between single quotes,
A comment consists of the hash character `#` and any following text until (not including) the next newline character. The initial `#` must not be part of a string literal started earlier. Comments are ignored entirely and do not form tokens.
-Identifiers and numeric literals share the same token formation rule. These tokens are formed from the *numeric characters* `Β―βˆžΟ€.0123456789` and *alphabetic characters* `_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ` and the oddball `𝕣`. Any sequence of these characters adjacent to each other forms a single token, which is a *numeric literal* if it begins with a numeric character and an *identifier* if it begins with an alphabetic character. Numeric literals are also subject to [numeric literal rules](literal.md), which specify which numeric literals are valid and which numbers they represent. If the token contains `𝕣` it must be either `𝕣`, `_𝕣`, or `_𝕣_` and is considered a special name (see below). As the value taken by this identifier can only be a modifier or composition, the uppercase character `ℝ` is not allowed.
+Identifiers and numeric literals share the same token formation rule. These tokens are formed from the *numeric characters* `Β―βˆžΟ€.0123456789` and *alphabetic characters* `_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ` and the oddball `𝕣`. Any sequence of these characters adjacent to each other forms a single token, which is a *numeric literal* if it begins with a numeric character and an *identifier* if it begins with an alphabetic character. Numeric literals are also subject to [numeric literal rules](literal.md), which specify which numeric literals are valid and which numbers they represent. If the token contains `𝕣` it must be either `𝕣`, `_𝕣`, or `_𝕣_` and is considered a special name (see below). As the value taken by this identifier can only be a modifier, the uppercase character `ℝ` is not allowed.
Following this step, the whitespace characters space and tab are ignored, and do not form tokens. Only these whitespace characters, and the newline character, which does form a token, are allowed.
@@ -15,8 +15,8 @@ Otherwise, a single character forms a token. Only the specified set of character
| Class | Characters
|-----------------------|------------
| Primitive Function | `+-Γ—Γ·β‹†βˆšβŒŠβŒˆ\|¬∧∨<>β‰ =≀β‰₯β‰‘β‰’βŠ£βŠ’β₯ŠβˆΎβ‰β†‘β†“β†•βŒ½β‰/β‹β’βŠβŠ‘βŠβŠ’βˆŠβ·βŠ”`
-| Primitive Modifier | `` ˜˘¨⌜⁼´` ``
-| Primitive Composition | `βˆ˜β—‹βŠΈβŸœβŒΎβŠ˜β—ΆβŽ‰βš‡βŸ`
+| Primitive 1-Modifier | `` ˜˘¨⌜⁼´` ``
+| Primitive 1-Modifier | `βˆ˜β—‹βŠΈβŸœβŒΎβŠ˜β—ΆβŽ‰βš‡βŸ`
| Special name | `π•¨π•©π•—π•˜π•€π•Žπ•π”½π”Ύπ•Š`
| Punctuation | `←↩→(){}βŸ¨βŸ©β€Ώβ‹„,` and newline