Andy Earnshaw wrote:
Yeah, I can see this being a problem. Invalidating in preparation to
redefine doesn't sound like a great solution, though, because you'd
still have the same problem when the next specification rolls around.
Right! Web browsers do not upgrade in lock-step, or even in a
ban/redefine two-step. N old versions smear across the market.
Opt-in sounds like a better solution, if pragmas are to be entered
into the specification then it could even become part of
use strict;
Your point applies here too, though. "use strict"; (did you forget the
quotes) has meaning in ES5, no meaning before, and therefore not likely
new meaning after ES5.
We do not plan to evolve "use strict". Nor do we plan to remove the
quotes (we've considered that at
http://wiki.ecmascript.org/doku.php?id=harmony:pragmas, deferred from
http://wiki.ecmascript.org/doku.php?id=harmony:proposals -- note
strikethrough). It's possible more pseudo-pragmas in quotes may be
standardized but as noted: wicked fight, requiring lots of data and
careful argumentation.
/be
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
