On Sat, 25 Jun 2011 05:50:05 +0200, Brendan Eich bren...@mozilla.com
wrote:
Let's get back to the problems with JS functions:
...
3. Tennent's principle of abstraction violations other than 'this'.
Why is this a *problem*?
I see having fully general non-local returns as a bigger problem
On Jun 26, 2011, at 11:44 PM, Brendan Eich wrote:
On Jun 26, 2011, at 3:05 PM, Allen Wirfs-Brock wrote:
On Jun 26, 2011, at 8:48 PM, Brendan Eich wrote:
But I still wonder if we wouldn't be better off restricting where super can
occur. I can't prove it, but we are following in the
On Jun 27, 2011, at 4:49 AM, Lasse Reichstein wrote:
On Sat, 25 Jun 2011 05:50:05 +0200, Brendan Eich bren...@mozilla.com wrote:
Let's get back to the problems with JS functions:
...
3. Tennent's principle of abstraction violations other than 'this'.
Why is this a *problem*?
We've
On Jun 27, 2011, at 12:49 PM, Lasse Reichstein wrote:
I guess the summary would be: I don't think Tennent's principle of
abstraction can be meaningfully applied to control flow when your abstraction
can survive the control flow that created it.
The success of such an abstraction for
I've been concerned about the schedule risk of classes for ES.next; following
are some thoughts about a minimal class feature that I believe satisfies the
most important needs while leaving room for future growth.
I think the bare-minimum requirements of classes would be:
- declarative class
On Jun 27, 2011, at 10:00 PM, David Herman wrote:
- standardizing prototype hierarchies (I'm of the opinion that superclass
constructors ought to be the prototype of subclass constructors in order to
inherit class properties)
+1
- providing idiomatic syntax for calling the superclass
- providing idiomatic syntax for calling the superclass constructor
But what about subclass method calling superclass method(s)?
In terms of priorities, I think super-constructors are the single most
important use case for super. But I think super-methods fall out naturally from
the
On Mon, Jun 27, 2011 at 10:13 PM, Brendan Eich bren...@mozilla.com wrote:
On Jun 27, 2011, at 10:00 PM, David Herman wrote:
I've been concerned about the schedule risk of classes for ES.next
Is the timeline posted somewhere?
- providing idiomatic syntax for calling the superclass
On Jun 27, 2011, at 10:50 PM, Peter Michaux wrote:
On Mon, Jun 27, 2011 at 10:13 PM, Brendan Eich bren...@mozilla.com wrote:
On Jun 27, 2011, at 10:00 PM, David Herman wrote:
I've been concerned about the schedule risk of classes for ES.next
Is the timeline posted somewhere?
We've talked
9 matches
Mail list logo
