>>If the Common Language Runtime doesn't support multiple inheritance, how is Eiffel.NET supposed to support it? I don't believe it can. Presumably Eiffel.NET will be different in some ways from the current version, just as VB.NET differs from VB 6, in order to support .NET's requirements.
>>
>
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/pdc_eiffel.asp <<

Thanks for the URL. Note that it describes Eiffel# (the .NET version) as differing from standard Eiffel in the area of multiple inheritance. Here is the pertinent passage:

"This brief introduction to Eiffel raises a few interesting issues for its integration into the .NET Framework. Maybe the most challenging is the support for multiple inheritance, since the common language run time was designed to support single inheritance only. Because Eiffel# must only use the common language run time, it has to follow the .NET Framework object model and thus disallows multiple inheritance of effective or partially-deferred classes. You may, however, multiple-inherit pure-deferred classes; in which case, they are generated as interfaces. The partially-deferred or effective parent class, if any, is the base type."

I don't know exactly what a pure-deferred class is but I do know that an interface is not the same as inheritance. This is at best a constrained and watered-down implementation of MI, as the white paper tacitly admits. (The section quoted above states in its concluding paragraph, "There are no other differences between Eiffel and Eiffel#.")

Mike