below On Sep 30, 2011, at 2:49 PM, Axel Rauschmayer wrote:
>> From: Waldemar Horwat <[email protected]> >> ... > > > 1. Super property references (mainly methods) > 2. Super constructor references > 3. Subclassing (mainly wiring the prototypes) > 4. Defining a class as compactly as possible (with subclassing, it is painful > that one has to assemble so many pieces). > 5. Having a standard construct that fosters IDE support. Currently there are > too many inheritance APIs out there, making IDE support nearly impossible. > 6. A platform on which to build future extensions (traits!). > > Allen’s object literal extensions give us #1 and #2. His prototype operator > gives us #3. #4 can be done via Allen’s pattern or by introducing the methods > - Function.prototype.withPrototypeProperties(props) > - Function.prototype.withClassProperties(props) > > I’m not sure about #5 (I’d consider class literals a plus here). I'd argue that my pattern also supports #5 as IDE's can recognize the pattern. An imperative class definition of all that most Smalltalk implementations every had and they generally had fine IDEs. > #6 can be postponed if we can get 1-5 by other means, but there will be a > price to pay if two competing ways of defining classes have to be used in > ES.next.next. > > -- > Dr. Axel Rauschmayer > > [email protected] > twitter.com/rauschma > > home: rauschma.de > blog: 2ality.com > > > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
