Daryle Walker wrote:
It is. And it checks for UCN validity, but only as long these are specified as \uxxxx or \Uxxxxxxxxx. (Wave leaves the actual translation into the execution character set to the compiler which processes the preprocessed Wave output - it acts solely on the character level).
This isn't internal-to-execution translation, but source-to-internal instead. Any non-basic characters, even if they have an actual symbol (like '$') should get resolved like the \u or \U notation. But this is dependent on whatever character set is used for a platform's text files.
Sure.
Either way, you should make this optional, and disabled by default, to allow Standards conformance when needed.
I've added the '$' to the basic source character set and it is allowed to be part of an identifier name now. I made this optional (configurable at compile time). Currently its on by default ('$' is recognised), but this arguable. [TRUNCATE]
I would suggest keeping '$' as an extended character, but put it (optionally) in the identifier-legal list.
Ok, agreed. '$' is allowed only inside identifiers (or makes up an identifier by itself).
That way we minimize the amount of power '$' gets. Also, you do allow \u and \U notation characters to be placed in identifiers, right?
Yes, it's allowed. Regards Hartmut