Posts: 312
Joined: 2006.10
Post: #16
Ah right, silly me. That does make a bit more sense Smile.

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?
Quote this message in a reply
Posts: 567
Joined: 2004.07
Post: #17
I generally avoid private anything anyways, and I will be keeping multiple-inheritance to a minimum.

It's not magic, it's Ruby.
Quote this message in a reply
Post Reply