> The beauty of VB.NET (since that is what actually started this thread....) is that both is possible there
I'll second that, although there are plenty of other beauties too.
As for multiple inheritance, there's a good deal of argument about its worth as well, since you have to keep track of the interfaces of each inherited class to make sure there's no conflicts in method definitions. Personally, I don't see lack of multiple inheritance as much of a handicap. Saves thinking, which I prefer to saving typing. (Perhaps that's abundantly clear from some of my posts?)
Yep; already figured that one out from your posts.....
As for the multiple inheritance; some argue that it causes a lot of pain (in the head mainly) others argue that sometimes it can be very useful (I'm one of them latter people...). But it was not mentioned by me as ment to be a handicap (although it sometimes can be one), it was more to point out that you can aggregate multiple other classes, but you can not inherit multiple classes.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.