On 2014/10/07 12:53:14, mathias wrote:
On 2014/10/07 11:06:50, wingo wrote:
> On 2014/10/07 10:52:59, Yang wrote:
> > can somebody point me to where this change is specified?
>
> The bug: http://code.google.com/p/v8/issues/detail?id=2892
> The spec:
>
http://people.mozilla.org/~jorendorff/es6-draft.html#sec-names-and-keywords
>
> Particularly:
>
> IdentifierStart ::
> UnicodeIDStart
> $
> _
> \ UnicodeEscapeSequence
>
> I can't speak to U+2E2F particularly; mathias probably knows more.
ES5 used to specify `IdentifierStart` and `IdentifierPart` based on a
list of
Unicode categories, one of which (`Lm`) happened to include U+2E2F. But
ES6
(mostly) just refers to `ID_Start` and `ID_Continue` instead.
U+2E2F has the `Pattern_Syntax` property and is thus not a valid
`ID_Start`
code
point.
Okay, so regarding the mongolian vowel separator, ES5 says
"ECMAScript implementations must recognise all of the white space characters
defined in Unicode 3.0. Later editions of the Unicode Standard may define
other
white space characters. ECMAScript implementations may recognise white space
characters from later editions of the Unicode Standard."
and ES6 says
"ECMAScript implementations must recognize as Whitespace code points listed
in
the "Separator, space" (Zs) category by Unicode 5.1. ECMAScript
implementations
may also recognize as Whitespace additional category Zs code points from
subsequent editions of the Unicode Standard."
The mongolian vovewl separator \u180E stopped being a white space since
Unicode
6.3.0, so we still have to recognize it as white space for Javascript.
https://codereview.chromium.org/626073002/
--
--
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.
