Updates:
Cc: [email protected] [email protected]
Comment #1 on issue 1829 by [email protected]: Harmony scoping should
enable strict mode
http://code.google.com/p/v8/issues/detail?id=1829
Hi Andy,
the reason for things being what they are is that our --harmony flag
currently serves the purpose to enable all of the harmony extensions
implemented so far that are backwards-compatible changes (or should I say,
addons) to the existing de-facto standard JS. The idea is that it will
eventually be enabled by default, and that in preparation for that it
should even today be possible to enable --harmony when starting Chrome,
surf the web and have existing code work (in addition to any newly written
code that might make use of harmony features).
Now, obviously the harmony proposal contains non-backward compatible
changes, where it treats existing code differently than ES3/ES5 did. AFAIK
we don't have a concrete plan yet for how we will deal with this. Maybe we
will need a "pure harmony" flag as an iterim solution that enables this
sort of changed behavior? But then again, the more orthogonal flags, the
more potential for bugs; and it could take decades until all non-harmony
compatible websites are updated. Probably it's best to wait and see how the
harmony proposal plays out before making a decision on this.
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
