Updates:
Cc: [email protected]
Comment #7 on issue 1972 by [email protected]: Incorrect treatment of
unicode escapes in keywords
https://code.google.com/p/v8/issues/detail?id=1972
From ES6 draft 11.6
Unicode escape sequences are permitted in an IdentifierName, where they
contribute a single Unicode code point to the IdentifierName. The code
point is expressed by the HexDigits of the UnicodeEscapeSequence (see
11.8.4). The \ preceding the UnicodeEscapeSequence and the u and { } code
units, if they appear, do not contribute code points to the IdentifierName.
A UnicodeEscapeSequence cannot be used to put a code point into an
IdentifierName that would otherwise be illegal. In other words, if a \
UnicodeEscapeSequence sequence were replaced by the SourceCharacter it
contributes, the result must still be a valid IdentifierName that has the
exact same sequence of SourceCharacter elements as the original
IdentifierName. All interpretations of IdentifierName within this
specification are based upon their actual code points regardless of whether
or not an escape sequence was used to contribute any particular code point.
So I guess this is pretty clear now.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
