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 right that the complicated mix of static and runtime checking required to implement eval and arguments in ES3 today.

Feature creep would be adding any more methods to Object, e.g. (although IIRC there's a case to be made by Allen for Object.hashcode ;-)).

More on an eval issue that I misremembered at the January meeting in a separate post. It and things like it we don't know about are the bigger threats to schedule than the strict mode refinements that amount to making certain identifiers reserved.

/be

On Feb 12, 2009, at 9:47 AM, Mark Miller wrote:

I'd be happier with the restriction than without.

2009/2/12 Allen Wirfs-Brock <allen.wirfs-br...@microsoft.com>
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? That does seem like a logical extension of the arguments that convinced us to ban strict mode eval declaration. Does anyone have a reason why such an assignment would be a reasonable thing.


Adding that assignment restriction is a bit of a feature creep but something that is probably manageable in the time we have left if the consensus is that it makes sense to do.


Thoughts?


Allen


_______________________________________________
Es-discuss mailing list
Es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss




--
Text by me above is hereby placed in the public domain

   Cheers,
   --MarkM

_______________________________________________
Es-discuss mailing list
Es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss

_______________________________________________
Es-discuss mailing list
Es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to