I've updated the description with more thorough information. The CL
preserves
the old semantics for const if the harmony scoping flag is not set, so at
the
moment it does not break compatibility.
However, the implementation follows the current draft specification when the
harmony scoping flag is set (with an exception: see the CL description),
i.e.
throwing early syntax errors for const and let declarations in classic and
strict mode. So yes, this will break compatibility once those changes become
active/visible.
http://codereview.chromium.org/8564001/
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
