C++—Hooboy
Ah right, silly me. That does make a bit more sense
.
So basically, all public and protected members of A, B and C become protected members of D - but you can't use any of them since B and C have there own copy of A's members, and D has a copy of A's, B's, and C's members which creates ambiguity within D?
.So basically, all public and protected members of A, B and C become protected members of D - but you can't use any of them since B and C have there own copy of A's members, and D has a copy of A's, B's, and C's members which creates ambiguity within D?
I generally avoid private anything anyways, and I will be keeping multiple-inheritance to a minimum.
It's not magic, it's Ruby.

