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
As an extension of #29 , allow all characters with Unicode general category letter or number to be used for alphanumeric identifiers (*), all characters with Unicode general category symbol to be used for symbol identifier and all characters with Unicode general category number to be used for numbers (**). Take care of additional end of line characters in Unicode.
(*) With, as it is already, the addition of the underscore and numbers not allowed as the first character.
(**) Optionally and not Unicode related, would be nice to allow underscores in numbers like Ada do, as it helps readability: ex. 1_234_567
The text was updated successfully, but these errors were encountered:
Thanks, I knew I've seen it with an SML compiler, but I was not suspecting it was already part of the standard.
About my original message, I was thinking using all characters with general category number may not be a good idea: I was thinking the character “ ² ” belongs to this category and writing 3² as 32 would be ambiguous. So I checked, and “ ² ” belongs to Other Number. So the Number category, but not the Other Number category (worth to be stressed).
As an extension of #29 , allow all characters with Unicode general category letter or number to be used for alphanumeric identifiers (*), all characters with Unicode general category symbol to be used for symbol identifier and all characters with Unicode general category number to be used for numbers (**). Take care of additional end of line characters in Unicode.
(*) With, as it is already, the addition of the underscore and numbers not allowed as the first character.
(**) Optionally and not Unicode related, would be nice to allow underscores in numbers like Ada do, as it helps readability: ex. 1_234_567
The text was updated successfully, but these errors were encountered: