Re: [webkit-dev] JavaScriptCore and ES6

2011-12-16 Thread Gavin Barraclough
Hi Andy, As you probably know, the ECMA TC39 committee is slowly approaching consensus on a new revision of the ECMAScript language. The interim results of this process have gone under various names: Harmony, ES.next, and ES6. They are the same thing. This mail is intended to open the

Re: [webkit-dev] JavaScriptCore and ES6

2011-12-16 Thread Anne van Kesteren
In general I think versioning is a bad idea, but out-of-band is even worse. We'd have to change Web Workers (both constructors and importScripts() would need to take some kind version-related information) and everyone on the platform would instead of simply using script have to resort back to

Re: [webkit-dev] JavaScriptCore and ES6

2011-12-16 Thread Brendan Eich
On Dec 16, 2011, at 1:24 AM, Anne van Kesteren wrote: In general I think versioning is a bad idea, but out-of-band is even worse. ES.next is going to have a use version 6; in-band pragma. /be ___ webkit-dev mailing list

[webkit-dev] JavaScriptCore and ES6

2011-12-15 Thread Andy Wingo
Hello all, As you probably know, the ECMA TC39 committee is slowly approaching consensus on a new revision of the ECMAScript language. The interim results of this process have gone under various names: Harmony, ES.next, and ES6. They are the same thing. This mail is intended to open the

Re: [webkit-dev] JavaScriptCore and ES6

2011-12-15 Thread Adam Barth
The versioning issues in ECMAScript are tough. We ran into these same problems when we were working with TC39 to formulate a versioning plan for what became ES5. None of the alternatives are really that great, but you likely need to pick one to make progress. I would caution you about adding

Re: [webkit-dev] JavaScriptCore and ES6

2011-12-15 Thread Andy Wingo
On Thu, 2011-12-15 at 10:36 -0800, Adam Barth wrote: I would caution you about adding more modes to ECMAScript. I agree. You probably know this, but I just realized that my original mail could have implied that I'm on TC39, which is not the case. Just making that particular point clear. :)

Re: [webkit-dev] JavaScriptCore and ES6

2011-12-15 Thread Brendan Eich
As you probably know, the ECMA TC39 committee is slowly approaching consensus on a new revision of the ECMAScript language. The interim results of this process have gone under various names: Harmony, ES.next, and ES6. They are the same thing. Hi Andy, one nit to pick: Harmony is the full