On Jul 12, 2011, at 11:28 AM, David Herman wrote:

> No pejorative overtones intended. We just don't yet have any decent 
> terminology for distinguishing the full ES.next front end from the 
> backwards-compatible one.

In the working draft of the specification I'm using "extended code" to mean the 
extended ES.next language constructors that will require opt-in access.  I also 
redefine "strict code" to encompass both ES5 strict mode mode and extended code.

Allen

_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to