Should multiple inheritance be totally avoided or as long as the classes
inherited are not derived from the same "root" class? Is that a good
practice to derive a class from a parent class and several other classes of
only pure virtual functions? Thanks!

Relevant Pages

Q: the dreaded diamond......pattern" that can occur with multiple inheritance.... tree node, and class Root represents the special case of Node, i.e. ...MyNode...(comp.object)

Re: Why ABCs make bad Interfaces..."Multiple Inheritance and Pure Abstract Classes ... an abstract class that has no data and only pure virtual functions....Bjarne Stroustrup: I had a lot of problems explaining that to people and never ...(comp.object)

Re: multiple inheritance..."andy" wrote in message ... > Should multiple inheritance be totally avoided or as long as the ... > practice to derive a class from a parent class and several other ... I know about problems with EBO and ...(comp.lang.cpp)

Re: multiple inheritance... class B: A {int varB;};... There are even more convoluted orders in practice, but this is the sort of stuff that tends to cause nasty sorts of little edge cases in practice. ... It is rare in practice that you need true multiple inheritance, in the sense of inheritance of implementation; multiple inheritance of interface is common, and this is as far as Java goes. ...(comp.lang.java.programmer)

Re: multiple inheritance... Strictly speaking, Java does support multiple inheritance, just ... This is because multiple inheritance of implementation is silly. ... class B: A {int varB;};... of little edge cases in practice....(comp.lang.java.programmer)