The global object in browsers

Brendan Eich brendan at
Tue Feb 17 18:38:25 PST 2009

On Feb 17, 2009, at 6:31 PM, Mark Miller wrote:

> Now that I think I understand "current" and how weak the legacy  
> constraints are, why not simply spec that your WindowProxy is the  
> object to treated as the ECMAScript global object? The consequence  
> would be that both f() and g() in your original example would return  
> 2.

That either opens a huge security hole, or imposes costly runtime  
checks on all lexical references to global variables.


More information about the Es-discuss mailing list