On 2014/09/10 13:53:09, marja wrote:
On 2014/09/10 13:48:58, Yang wrote:
> On 2014/09/10 13:39:28, rossberg wrote:
> > Not specific to this CL, but I wonder if we shouldn't eventually
change
these
> > names to ASCII and UCS2, for more clarity...
>
> Rather Latin1 instead of ASCII.
Yep, not ASCII, since it actually is Latin1, not ascii. However, the V8
term
for
it seems to be "one byte" - it's used everywhere.
Yes, makes sense.
Why "UCS2" though? Isn't UTF-16 a much more well known term? Do you mean
it's
actually not UTF-16?
It's not the same thing -- which is exactly why I think we should be more
explicit. I don't actually understand which way we currently interpret
"TWO_BYTE" input. (JavaScript used to assume UCS-2, but with ES6 that's
getting
kind of reinterpreted as UTF-16, at least in some places.)
https://codereview.chromium.org/366153002/
--
--
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.
