Language modes (Was: Block scoping and redeclarations)
brendan at mozilla.com
Wed Aug 24 09:08:22 PDT 2011
On Aug 24, 2011, at 2:08 AM, Andreas Rossberg wrote:
>> That's not to say that I couldn't live with more fine-grained rules, I
>> just don't consider them worthwhile. Ultimately, we want to morally
>> deprecate "var" for Harmony mode, so introducing too many extra rules
>> around it seems a bit unjustified, unless there is a very good reason.
> Btw, we had this amusing discussion in July how to name the different
> language modes without stepping on people's toes. How about "classic",
> "strict", and "modern"?
I once made the mistake of using "_NEW" as a name part for an opcode in SpiderMonkey. Got old fast.
We want few modes, ideally only RFC4329 version numbers on one line, not a lattice. This is why Harmony is based on ES5 strict and we do not want an ES6 stricter strict ("use really strict").
The argument in July, which I was lucky enough to (mostly) miss, seemed spec jargon bikeshedding. "Extended mode" vs. something else.
More information about the es-discuss