Re:Prototypes Are Not Classes
by angersock on Sunday January 19, 2014 @02:26PM
(#7085580)
MI still sends shivers down my spine, having spent time in the C++. Just say no.
[ Parent
| on HN ]
So C++ got multiple inheritance wrong... That doesn't mean it must be rejected in all cases.
What are the cases where MI is better than mix-ins or component architectures?
NewtonScript had a neat concept of heterogeneous multiple inheritance: Its "objects" had a prototype-like inheritance chain and a container inheritance chain.
If client-side JavaScript had this design, there would be no need for the DOM to have a special event mechanism that lives outside of method handling: DOM elements would simply have method handlers and the dispatch system would handle prototype and container inheritance.
> NewtonScript had a neat concept of heterogeneous multiple inheritance: Its "objects" had a prototype-like inheritance chain and a container inheritance chain.
See also HyperCard/HyperTalk...
Maybe just in some corner cases.
However Eiffel, OCaml and Python MI implementations seem to be implemented in a more sane way.
CLOS
Beware, Self inheritance is not class-based inheritance, and thus Self MI has very little relation to C++'s MI.