Comment #4 on issue 375 by [email protected]: Optimize handling of catch
variables.
http://code.google.com/p/v8/issues/detail?id=375
The scope bug you report is working as intended for compatibility.
The current behavior is indeed compatible with ES3. It is incompatible with
ES5, even without
strict mode. It is fatally incompatible with ES5-strict, as the most
important feature of ES5-
strict is that it is statically scoped.
How do you keep track of features which must be changed when making the
transition from
ES3 compatibility to ES5 compatibility? If you have a tag for this, I
suggest it be applied to this
issue. Regarding ES5, this is a bug, not a feature request.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
