How much of this have you actually done? Vs. read theory for purposes of debate?

By simulating MI Bonnie is talking about the ability to inherit from your base class for that type of object (I.E. the Employee inherit Person), and then implement interfaces for Sorting, Comparing, etc. So you can you interfaces to enforce good class design.

>>>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?