Re: (Request/propose) license change

2013-09-03 Thread Anne van Kesteren
On Tue, Sep 3, 2013 at 2:56 AM, Brendan Eich bren...@mozilla.com wrote: Anyway, we your faithful TC39ers will take this up with Ecma people. That sounds great! It has been an issue recently with W3C too, where tan...@mozilla.com has been championing CC0. FWIW, rationale for this basically

Promises: final steps

2013-09-03 Thread Anne van Kesteren
As many of you hopefully know, we're trying to nail down the design of promises in JavaScript so we can declare consensus on it and start shipping it in implementations. If you're interested in the particulars I strongly recommend reading through

Re: Promises: final steps

2013-09-03 Thread Tab Atkins Jr.
On Tue, Sep 3, 2013 at 6:37 AM, Anne van Kesteren ann...@annevk.nl wrote: As many of you hopefully know, we're trying to nail down the design of promises in JavaScript so we can declare consensus on it and start shipping it in implementations. If you're interested in the particulars I strongly

Re: Proposal to fix super and new inconsistency, future-proofing broader uses of new operator

2013-09-03 Thread Allen Wirfs-Brock
An interesting proposal, but I'm not yet sold. Here are some of the issue I see: 1) By newing a function an ES programmer is expressing a clear intent to use the body the body of the function as part of the instantiation process. It would be counter intuitive to not execute the body of a

Re: Removal of NoIn grammar productions and for-loop parsing

2013-09-03 Thread Allen Wirfs-Brock
On Sep 1, 2013, at 7:42 PM, Brendan Eich wrote: ... Ambiguity is not a matter of preference. We need to validate the ES6 grammar. Until then, please put back the NoIn productions. They were not there only because of the silly and unwanted initialiser option for 'for (var x = y of z)'.

Re: Removal of NoIn grammar productions and for-loop parsing

2013-09-03 Thread Brendan Eich
Allen Wirfs-Brock mailto:al...@wirfs-brock.com September 3, 2013 10:45 AM Yup, we went off-track on this at the meeting. But Waldemar's point about arrow functions is still valid. We are going to need to have ArrowFunctionNoIn to disallow things like: for (f = x = x in foo;;) For sure.

Everything is an expression

2013-09-03 Thread musicdenotation
var x = if (condition) a; else b; var y = {let x = m; let y = n; x+2*y;} Why does JavaScript don't support these? --- To Ecma International: Release the ECMAScript specification under Creative Commons Attribution 1.0+ / Open Web Foundation License 0.8+

Re: Everything is an expression

2013-09-03 Thread Brendan Eich
Because make it look like Java was the rule, and what you propose will break compatibility with unminified semicolon-free code that would be minified by a syntax-aware minifier to insert semicolons. I 3 Algol 68 too, but please work on higher priorities. /be musicdenotat...@gmail.com

RE: 'function *' is not mandatory

2013-09-03 Thread François REMY
Hi, I'm back. Not sure I totally figured it out, but I thought it was probably time to yield my reasoning before iterating further ;-) To achieve a different result, I figured out we probably needed to start from a different sets of initial assumptions. So here are my new set of assumptions: