Re: assignment to eval in strict code

2009-02-18 Thread Mark Miller
On Wed, Feb 18, 2009 at 8:40 AM, Allen Wirfs-Brock < allen.wirfs-br...@microsoft.com> wrote: > >-Original Message- > >From: Mark S. Miller [mailto:erig...@google.com] > >Sent: Thursday, February 12, 2009 4:58 PM > > > >Good. So does anyone object to ES3.1-strict imposing the same > >restri

RE: assignment to eval in strict code

2009-02-18 Thread Allen Wirfs-Brock
>-Original Message- >From: Mark S. Miller [mailto:erig...@google.com] >Sent: Thursday, February 12, 2009 4:58 PM > >Good. So does anyone object to ES3.1-strict imposing the same >restrictions on the magic name "arguments" as we will on "eval"? > In strict mode, "arguments" is already defin

RE: assignment to eval in strict code

2009-02-13 Thread Allen Wirfs-Brock
-discuss Subject: Re: assignment to eval in strict code On Thu, Feb 12, 2009 at 5:17 PM, Waldemar Horwat mailto:walde...@google.com>> wrote: Allen Wirfs-Brock wrote: Now that we have decided that all declarations of the identifier "eval" are banned from strict code a related question

Re: assignment to eval in strict code

2009-02-13 Thread David-Sarah Hopwood
Allen Wirfs-Brock wrote: > Now that we have decided that all declarations of the identifier > "eval" are banned from strict code a related question has come up > from one of the implementers of our strict mode prototype implementation. > Why does Es3.1 still allow assignment to the identifier "eval

Re: assignment to eval in strict code

2009-02-12 Thread Mark Miller
On Thu, Feb 12, 2009 at 5:17 PM, Waldemar Horwat wrote: > Allen Wirfs-Brock wrote: > >> Now that we have decided that all declarations of the identifier "eval" >> are banned from strict code a related question has come up from one of the >> implementers of our strict mode prototype implementation.

Re: assignment to eval in strict code

2009-02-12 Thread Waldemar Horwat
Allen Wirfs-Brock wrote: Now that we have decided that all declarations of the identifier “eval” are banned from strict code a related question has come up from one of the implementers of our strict mode prototype implementation.Why does Es3.1 still allow assignment to the identifier “eval”

Re: assignment to eval in strict code

2009-02-12 Thread Mark S. Miller
2009/2/12 Brendan Eich : > I wouldn't worry about feature creep in terms of strict mode forbidding > certain identifiers in unambiguous grammatical positions. Some > implementations already have to work harder if arguments is the left-hand > side of assignment within a function. Such parser tweaks

Re: assignment to eval in strict code

2009-02-12 Thread Brendan Eich
I wouldn't worry about feature creep in terms of strict mode forbidding certain identifiers in unambiguous grammatical positions. Some implementations already have to work harder if arguments is the left-hand side of assignment within a function. Such parser tweaks are also easier to get ri

Re: assignment to eval in strict code

2009-02-12 Thread Mark Miller
I'd be happier with the restriction than without. 2009/2/12 Allen Wirfs-Brock > Now that we have decided that all declarations of the identifier "eval" > are banned from strict code a related question has come up from one of the > implementers of our strict mode prototype implementation.Why

assignment to eval in strict code

2009-02-12 Thread Allen Wirfs-Brock
Now that we have decided that all declarations of the identifier "eval" are banned from strict code a related question has come up from one of the implementers of our strict mode prototype implementation.Why does Es3.1 still allow assignment to the identifier "eval" within strict code? Tha