I'd like to mention that this is a classic example of how inheritance is taught in OO text books and is also a classic example of how to not use inheritance in the real world.
I wish I could eloquently explain why this is such a bad idea. The basic problem is that inheritance is a very tight binding between types and it can easily tie you up down the road and make things very difficult. You are usually better off having one object contain a reference to another over having the one inherit from the other.
- tye (but my friends call me "Tye")In reply to (tye)Re: how do I do multiple inheritance
by tye
in thread how do I do multiple inheritance
by rdww
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |