obsoleting the "new" keyword

Mark Miller erights at gmail.com
Sun Jan 18 22:23:41 PST 2009


2009/1/18 Brendan Eich <brendan at mozilla.com>:
> The other unreserved context in JS1.7 and later is after the 'function'
> keyword. Unambiguous, complementary, useful for some cases. It's easy to
> tweak ES3.1's grammar to allow keywords in this context too. Thoughts?

It would be surprising to be able to say "function if(x) {return x;}"
but not "if(33);". On property names, we symmetrically unreserve both
the definition (by object literal) and the use (by ".").

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

    Cheers,
    --MarkM


More information about the Es-discuss mailing list