July 19, 2002
Q: Why doesn't the Java language support multiple inheritance?
A: Whenever you find yourself asking why Java has or does not have some feature, consider the design goals behind the Java language. With that in mind, I started my search by skimming through "The Java Language Environment" by James Gosling and Henry McGilton (Sun Microsystems), a white paper published in May 1996 that explains some of the reasoning behind Java's design.
As the white paper states, the Java design team strove to make Java:
- Simple, object oriented, and familiar
- Robust and secure
- Architecture neutral and portable
- High performance
- Interpreted, threaded, and dynamic
The reasons for omitting multiple inheritance from the Java language mostly stem from the "simple, object oriented, and familiar" goal. As a simple language, Java's creators wanted a language that most developers could grasp without extensive training. To that end, they worked to make the language as similar to C++ as possible (familiar) without carrying over C++'s unnecessary complexity (simple).
In the designers' opinion, multiple inheritance causes more problems and confusion than it solves. So they cut multiple inheritance from the language (just as they cut operator overloading). The designers' extensive C++ experience taught them that multiple inheritance just wasn't worth the headache.
Note: For a discussion of the diamond problem, a classic multiple inheritance challenge, read Bill Venners's "Designing with Interfaces" (JavaWorld, December 1998) and Tony Sintes's "Java Diamonds Are Forever" (JavaWorld, March 2001).
Instead, Java's designers chose to allow multiple interface inheritance through the use of interfaces, an idea borrowed from Objective C's protocols. Multiple interface inheritance allows an object to inherit many different method signatures with the caveat that the inheriting object must implement those inherited methods.
Multiple interface inheritance still allows an object to inherit methods and to behave polymorphically on those methods. The inheriting object just doesn't get an implementation free ride. For an excellent discussion of interface inheritance, read Wm. Paul Rogers's "Reveal the Magic Behind Subtype Polymorphism" (JavaWorld, April 2001).
Learn more about this topic
- "The Java Language Environment," James Gosling and Henry McGilton (Sun Microsystems, May 1996)
- Bill Venners's "Designing with Interfaces" (JavaWorld, December 1998)
- Tony Sintes's "Java Diamonds Are Forever" (JavaWorld, March 2001)
- Wm. Paul Rogers's "Reveal the Magic Behind Subtype Polymorphism" (JavaWorld, April 2001)
- For more articles on Java's design, browse the Core Java section of JavaWorld's Topical Index
- Want more? See the Java Q&A index page for the full Q&A catalog
- For more than 100 insightful Java tips from some of the best minds in the business, visit JavaWorld's Java Tips index page
- Learn Java basics in our Java Beginner discussion
- Sign up for JavaWorld's free weekly Core Java email newsletter
- You'll find a wealth of IT-related articles from our sister publications at IDG.net