why java does not support multiple inheritance????????????????
If it is to eliminate ambiguity,even interface also causes ambuiguity.....
Please answer this in details.....................................
Welcome to the Java Programming Forums
The professional, friendly Java community. 21,500 members and growing!
The Java Programming Forums are a community of Java programmers from all around the World. Our members have a wide range of skills and they all have one thing in common: A passion to learn and code Java. We invite beginner Java programmers right through to Java professionals to post here and share your knowledge. Become a part of the community, help others, expand your knowledge of Java and enjoy talking with like minded people. Registration is quick and best of all free. We look forward to meeting you.
>> REGISTER NOW TO START POSTING
Members have full access to the forums. Advertisements are removed for registered users.
LinkBack URL
About LinkBacks
why java does not support multiple inheritance?
why java does not support multiple inheritance????????????????
If it is to eliminate ambiguity,even interface also causes ambuiguity.....
Please answer this in details.....................................
Related threads:
Re: why java does not support multiple inheritance?
i cant state any definitive answer for you, but i got something around from google
Java Multiple Inheritance
Re: why java does not support multiple inheritance?
Questions like these are a bit pointless. Why should Java support multiple inheritance? Why do you think you need it?Originally Posted by venkatsairam
Useful links: How to Ask Questions the Smart Way | Use Code Tags | Java Tutorials
Static Void Games - Play indie games, learn from game tutorials and source code, upload your own games!
chronoz13 (January 18th, 2012)
Re: why java does not support multiple inheritance?
As the reference to interfaces might have suggested, Java does have multiple inheritance: an object can inherit methods from a number of supertypes and behave polymorphically on those methods.
What the object does *not* get is implementation inherited from multiple superclasses. There is one direct superclass. It is with *implementation* being inherited from diverse ancestors that amibiguity arises.
I have no clue about the historical question of why particular people made the particular decisions they did. But you might want to read Gosling and McGilton's famous white paper introducing the language. In 3.3.7 Java Language Interfaces they motivate interfaces as a way of enhancing single inheritance of implementation.
Reply With Quote