There is some ambiguity between the spoken-language spec and the Text Grammar about whether comment starts delimit the end of "numeric_entities" and "sexp_keyword_entities."
Consider the below:
2004T/* comment after Timestamp with no whitespace*/
Per the grammar, that should be legal as comments are included in ws.
There is some ambiguity between the spoken-language spec and the Text Grammar about whether comment starts delimit the end of "numeric_entities" and "sexp_keyword_entities."
Consider the below:
Per the grammar, that should be legal as comments are included in
ws
.But per the spoken-language spec, '/' is not a "stop-character."
This same ambiguity exists for integers, real numbers and keywords.
The
ion
CLI considers following any of the above a parse error. I have not canvassed other implementations.