-
June 16th, 2010, 04:58 PM
#1
Multiple inheritance?
Why doesn't .NET support multiple inheritance?
-
June 17th, 2010, 03:44 AM
#2
Re: Multiple inheritance?
Why should it? Multiple inheritance can lead to some problems (such as the diamond problem) and it was decided that it would not support. However it promotes designing for interfaces and you can implement as many interfaces as you want.
Is there some scenario where you can't live without MI? I don't think so.
-
June 17th, 2010, 06:01 AM
#3
Re: Multiple inheritance?
![Quote](images/misc/quote_icon.png) Originally Posted by cilu
Is there some scenario where you can't live without MI? I don't think so.
I could use a hand trowel to dig over my garden if I had to, but I'd still prefer to use a spade. Using a 'workaround' is not the same as using the real tool.
"It doesn't matter how beautiful your theory is, it doesn't matter how smart you are. If it doesn't agree with experiment, it's wrong."
Richard P. Feynman
-
June 17th, 2010, 07:38 AM
#4
Re: Multiple inheritance?
One reason .NET doesn't support MI is that it is designed to be cross-language. Most OO languages don't support MI.
Kevin
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|