You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 25, 2021. It is now read-only.
For faster and more language independent behaviour, the attribute name should
not be stored as a string, but as an integer. This approach gives greater
freedom for dialect implementers, like redefining the same name-number
depending on the identifier (scoping). But since JS and JSON are not supporting
the ability to have integers as keys, and in some languages having a hash-map is
a difficulty, attributes should be an array of fixed length arrays, as follows:
attribute ::= <array of attribute_pairs>
attribute_pair ::= unsigned integer, string
eg.
[0, [[0, "#"]], null];
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Proposed Enhancements (PRT v3.0)
For faster and more language independent behaviour, the attribute name should
not be stored as a string, but as an integer. This approach gives greater
freedom for dialect implementers, like redefining the same name-number
depending on the identifier (scoping). But since JS and JSON are not supporting
the ability to have integers as keys, and in some languages having a hash-map is
a difficulty, attributes should be an array of fixed length arrays, as follows:
eg.
The text was updated successfully, but these errors were encountered: