Newly revised Section 10 for ES3.1.
Allen.Wirfs-Brock at microsoft.com
Wed Jul 9 22:05:18 PDT 2008
I'm also confused about this. My understanding was, other than perhaps some of the details I was specifically looking for feedback on, that what I specified was generally what ES4 was planning on doing.
From: es4-discuss-bounces at mozilla.org [mailto:es4-discuss-bounces at mozilla.org] On Behalf Of Mark S. Miller
Sent: Wednesday, July 09, 2008 7:13 PM
To: Brendan Eich
Cc: Herman Venter; Douglas Crockford; es3.x-discuss at mozilla.org; es4-discuss at mozilla.org; Pratap Lakshman (VJ#SDK)
Subject: Re: Newly revised Section 10 for ES3.1.
On Wed, Jul 9, 2008 at 7:02 PM, Brendan Eich <brendan at mozilla.org<mailto:brendan at mozilla.org>> wrote:
On Jul 9, 2008, at 6:58 PM, Mark S. Miller wrote:
Hi Maciej, IIUC, these examples work the same in Allen's proposal as the do in ES4. If this does break the web, doesn't ES4 have exactly the same problem?
I had not understood that. I knew that new keywords were switched by the ES4 opt-in, and I have been following what ES4 switches based on strictness, but I probably haven't paid enough attention to ES4 opt-in. Besides keywords, what other elements of ES4 are switched on opt-in rather than strictness? Are all four combinations of opt-in vs strictness possible? Is opt-in per execution context (script) or per global object (frame)? A link to the relevant docs is an adequate answer. Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Es4-discuss