>>I only wanted to say that MI is debatable, to say the least, so saying "there is nothing wrong" with it is too strong.
>
>And all I meant by that was "there is nothing wrong" with using Interfaces to *simulate* multiple inheritance. Basically, to get the good stuff without having the bad stuff.
>
>~~Bonnie

What part of MI bad stuff is avoided by simulation? Simulated or not, MI can lead to spaghetti - you have the top-down class hierarchy, then possibly a top-down interfaces hierarchy, then the MI going the other way.
Why was true MI left out of the C# compiler?