5 ms·
MI still sends shivers down my spine, having spent time in the C++. Just say no.
by angersock 13y ago
MI still sends shivers down my spine, having spent time in the C++. Just say no.
- clhodapp 13y agoSo 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]
- masklinn 13y agoBeware, Self inheritance is not class-based inheritance, and thus Self MI has very little relation to C++'s MI.
- roel_v 13y agoOK, I'll bite. Please tell me what exactly your problem was.