This confuses user-level opt-in and developer-level opt in. As I
understand it,
the --harmony flag is supposed to be simulating a browser in the future
where a
Harmony-based ES.next standard has been ratified. At that point there will
still be three modes (classic, strict, extended) and classic mode will still
need to handle all the pages where the developer has not opted into strict
or
harmony semantics. Those pages contain 'const' and we won't want to break
them
when that day comes.
Therefore, of the two modes with --harmony we only need the one that is
currently reserved for the natives.
http://codereview.chromium.org/8564001/
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
