Inscrivez-vous ou connectez-vous pour rejoindre votre communauté professionnelle.
Dear as mentioned in many location over the internet that c# doesn't support multiple inheritance due to that multiple inheritance will lead by default to multiple implementation which will increase code architect complexity and definitely will increase the conflict probability.
Multiple Inheritance will not be supported
Supported : Single , Multilevel , Hiearchical , Hybrid
Due to the complexity of a code multiple inheritance is not been supported in C# or in DOT.NET but DOT.NET or C# supports multiple interfaces.
Different languages actually have different expectations for how MI works. For example, how conflicts are resolved and whether duplicate bases are merged or redundant. Before we can implement MI in the CLR, we have to do a survey of all the languages, figure out the common concepts, and decide how to express them in a language-neutral manner. We would also have to decide whether MI belongs in the CLS and what this would mean for languages that don't want this concept (presumably VB.NET, for example). Of course, that's the business we are in as a common language runtime, but we haven't got around to doing it for MI yet.
The number of places where MI is truly appropriate is actually quite small. In many cases, multiple interface inheritance can get the job done instead. In other cases, you may be able to use encapsulation and delegation. If we were to add a slightly different construct, like mixins, would that actually be more powerful?
Multiple implementation inheritance injects a lot of complexity into the implementation. This complexity impacts casting, layout, dispatch, field access, serialization, identity comparisons, verifiability, reflection, generics, and probably lots of other places.
Multiple Inheritance. As it will lead to code complexity etc ..
Avez-vous besoin d'aide pour créer un CV ayant les mots-clés recherchés par les employeurs?
