Home / Docs / Specification / 30. Packages and dependencies
30.1 Lexical rules
Release v0.4.0
- The lexer of spec/01.
ita.una,ita.lockanditaty.unaare read by the lexer of spec/01: UTF-8 without a byte order mark, two-space indentation,--comments, no tabs, the control characters of spec/01 §1 rule 6 rejected, identifiers, and integer and text literals as spec/01 §4 and§6state. Two differences hold in these files only.- A version token.
version_lit = num "." num [ "." num ] [ "-" pre { "." pre } ], wherenumis0or digits without a leading zero, andpreis[0-9A-Za-z]+, a numericprewithout a leading zero. It is matched before integers, so1.4and0.1.0are versions here. A malformed version, such as01.2,1.2.3.4or1.2.3+build, is an error. - Text without interpolation. A text literal MUST NOT contain
{or}other than as\{and\}: nothing is interpolated.
- A version token.
- No keywords. No word of these files is a keyword or a reserved word:
from,in,trustedandprofileare words of the grammar where it names them. No word of these files becomes a keyword of a module. - Nothing runs. There are no expressions, no interpolation, no conditions, no includes and no environment variables, and nothing else runs when a package is read, checked or built: there are no install scripts, build scripts or hooks of any kind.
- Bounds.
ita.unaanditaty.unahold at most 1 MiB, andita.lockat most 16 MiB; past that, the file is refused whole, at its start.