|
|
1 год назад | |
|---|---|---|
| .. | ||
| README.md | a1655b6858 Tuples and tuple indexing (#3646) | 2 лет назад |
| comments.md | 33f26bd37b Added design of comments in design docs (#2641) | 3 лет назад |
| numeric_literals.md | a1655b6858 Tuples and tuple indexing (#3646) | 2 лет назад |
| string_literals.md | c974a77314 Added newline example and clarifications for string_literals.md (#2966) | 2 лет назад |
| symbolic_tokens.md | 58c106010c Updates to design docs to reflect accepted proposals (#3254) | 2 лет назад |
| whitespace.md | b7df523dc8 Fix cross-file links in non-proposal files (#1010) | 4 лет назад |
| words.md | e257051612 No predeclared identifiers, `Core` is a keyword (#4864) | 1 год назад |
The first stage of processing a source file is the division of the source file into lexical elements.
A lexical element is one of the following:
a literal:
a comment
The sequence of lexical elements is formed by repeatedly removing the longest initial sequence of characters that forms a valid lexical element, with the following exception:
. or -> token, with no
intervening whitespace, a real literal is never formed. Instead, the token
will end no later than the next . character. For example, tuple.1.2 is
five tokens, tuple . 1 . 2, not three tokens, tuple . 1.2.
However, tuple . 1.2 is lexed as three tokens.