indirect eval spec too severe?

David-Sarah Hopwood david.hopwood at industrial-designers.co.uk
Sun Jan 25 00:24:51 PST 2009


Brendan Eich wrote:
> On Jan 24, 2009, at 4:51 PM, Mark Miller wrote:
> 
>> The current spec language allows the global eval property to be, in
>> effect, either mutable or not, benefiting no one. If we need to allow
>> correct programs to be able to mutate it (in an initial environment in
>> which it has not yet been frozen), then we should change the spec to
>> require it to be initially mutable, so that correct programs can rely
>> on this.
> 
> ES3 already requires eval to be a mutable global property, [...]

No, it does not, because attempting to assign global 'eval' may instead
throw EvalError (ES3 section 15.1.2.1).

-- 
David-Sarah Hopwood


More information about the Es-discuss mailing list