Thanks Allen, Domenic, Andreas! Point taken.
I now remember why I originally started to use the word “subtyping”: I wanted a verb that means deriving a new constructor from an existing constructor C. And I didn’t want to say “extend C”, because that term was already in use in the JS community (Underscore etc.). With ES6, “subclassing” works, because there are classes, but I wouldn’t want to use it for ES5. Suggestions for a better word are welcome. Axel On Jul 1, 2013, at 19:34 , Andreas Rossberg <rossb...@google.com> wrote: > On 1 July 2013 19:00, Axel Rauschmayer <a...@rauschma.de> wrote: >> Similarly: @@create (which enables the subtyping of built-ins). >> ^^^^^^^^ >> subclassing >> >> Curious: is that an important distinction? To me, a (sub)class is the >> implementation of a (sub)type. > > Inheritance Is Not Subtyping, see this classic paper: > > http://users.csc.calpoly.edu/~gfisher/work/specl/documentation/related-work/formal-semantics/p125-cook.pdf > > Unfortunately, most OO languages still confuse the two. > > (JS does not really have subtyping anyway, though.) -- Dr. Axel Rauschmayer a...@rauschma.de home: rauschma.de twitter: twitter.com/rauschma blog: 2ality.com
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
