4 ms·
So C++ got multiple inheritance wrong... That doesn't mean it must be rejected in all cases.
by clhodapp 13y ago
So C++ got multiple inheritance wrong... That doesn't mean it must be rejected in all cases.
- angersock 13y agoWhat are the cases where MI is better than mix-ins or component architectures?
- pjmlp 13y agoMaybe just in some corner cases. However Eiffel, OCaml and Python MI implementations seem to be implemented in a more sane way.
- raganwald 13y agoNewtonScript 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.
- lispm 13y ago> 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...
- mtraven 13y agoCLOS
- deleted 13y ago[deleted]