News for hackers. Stuff that matters.
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.
Re:Prototypes Are Not Classes by clhodapp on Sunday January 19, 2014 @02:36PM (#7085620)
So C++ got multiple inheritance wrong... That doesn't mean it must be rejected in all cases.
Re:Prototypes Are Not Classes by angersock on Sunday January 19, 2014 @03:37PM (#7085888)
What are the cases where MI is better than mix-ins or component architectures?
Re:Prototypes Are Not Classes by raganwald on Sunday January 19, 2014 @04:25PM (#7086061)
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.

Re:Prototypes Are Not Classes by lispm on Sunday January 19, 2014 @05:58PM (#7086446)
> 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...

Re:Prototypes Are Not Classes by pjmlp on Sunday January 19, 2014 @03:59PM (#7085967)
Maybe just in some corner cases.

However Eiffel, OCaml and Python MI implementations seem to be implemented in a more sane way.

Re:Prototypes Are Not Classes by mtraven on Monday January 20, 2014 @01:49AM (#7087953)
CLOS
Re:Prototypes Are Not Classes by masklinn on Sunday January 19, 2014 @04:44PM (#7086128)
Beware, Self inheritance is not class-based inheritance, and thus Self MI has very little relation to C++'s MI.
Re:Prototypes Are Not Classes by roel_v on Monday January 20, 2014 @05:38AM (#7088768)
OK, I'll bite. Please tell me what exactly your problem was.