On Oct 4, 2011, at 2:37 AM, Erik Arvidsson wrote: > On Mon, Oct 3, 2011 at 17:25, Brendan Eich <[email protected]> wrote: >> If so we are at an impasse. To get past it, we would need to agree on >> declarative syntax and semantics preventing use before initialization. We >> can try to do that again, see if anyone has changed minds. > > I don't agree that we need to agree on a semantic that prevents use > before initialization for ES.next. Like I've previously stated both > Python and ES5 gets by without this.
Right, but IIRC at least Waldemar disagrees, or at least (more below) wants to future-proof carefully. > The proposal we were talking about (last hour of the F2F) was > something even simpler than what we have at the wiki. It did involve > using object literal for the class body and no special form for the > constructor. This makes things simpler For us, perhaps. For users, less so. If we add class syntax, it's not hard to make the class body it's own thing. I think this is better for usability than recycling ObjectLiteral. I acknowledge your point that mixing declarations in the body as directly contained elements suggests methods close over them. My most-minimal solution, proposed on the list and IIRC at the meeting, is to forbid non-method declarations in class bodies, outside of class: sections if we choose to support that. > but the main downside with that > is that it is not as easily extended to add const and whatever feature > we might want in the future. That does seem to ask for trouble, on the very basis that led to Hoare being invoked. /be _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
