On Apr 13, 2011, at 9:06 PM, David Herman wrote: >>> It'll be the WindowProxy as usual, in top level code. Dave has addressed >>> what it will be in a module recently. >> >> I have to look on Dave's explanation, seems I missed it. But this >> WindowProxy won't be assessable then, right? Will it be possible to define a >> new global property/variable at all at runtime depending on condition? > > I think what Brendan means is that legacy script (that doesn't opt in to the > new version) will continue to be ES5 and will continue to use the window > object as the global scope frame. But the window won't be the global > environment record in Harmony.
Ok, or maybe I was just out of date ;-). > In Harmony (as you know, Dmitry), the global scope is separate from the > window object. At Harmony top-level, |this| is bound to an object that > reflects the global scope, but it's not possible to do things like delete > bindings from it, and it's a separate object from the window object. Cool -- is this spec'ed yet? /be _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
