Comments on: Multiple Inheritance in Java http://www.erik-rasmussen.com/blog/2006/10/23/multiple-inheritance-in-java/ Thoughts and photos from an American living in Spain. Fri, 05 Dec 2008 12:32:28 +0000 http://wordpress.org/?v=abc By: erik http://www.erik-rasmussen.com/blog/2006/10/23/multiple-inheritance-in-java/#comment-744 erik Mon, 21 May 2007 20:12:01 +0000 http://www.erik-rasmussen.com/blog/2006/10/23/multiple-inheritance-in-java/#comment-744 An "Add-In" for an IDE? Which IDE? Anyway, I look forward to seeing what you come up with. An “Add-In” for an IDE? Which IDE?

Anyway, I look forward to seeing what you come up with.

]]> By: johanatan http://www.erik-rasmussen.com/blog/2006/10/23/multiple-inheritance-in-java/#comment-743 johanatan Mon, 21 May 2007 19:53:28 +0000 http://www.erik-rasmussen.com/blog/2006/10/23/multiple-inheritance-in-java/#comment-743 P.S. I wouldn't call this a 'flaw' either. It's more of a deficiency. But, I'm currently working on the Add-In that I hoped would fill in the gap. I'll post a link to it when it's done. P.S. I wouldn’t call this a ‘flaw’ either. It’s more of a deficiency. But, I’m currently working on the Add-In that I hoped would fill in the gap. I’ll post a link to it when it’s done.

]]> By: johanatan http://www.erik-rasmussen.com/blog/2006/10/23/multiple-inheritance-in-java/#comment-680 johanatan Thu, 19 Apr 2007 19:49:08 +0000 http://www.erik-rasmussen.com/blog/2006/10/23/multiple-inheritance-in-java/#comment-680 I'm not a dogmatic C++ programmer, but I do enjoy having the option to use multiple inheritance. It saves you from having to 'wrap' all your method calls to the inner static. And, also you aren't limited to using a static (i.e., your example could have had and used members in the interface). Of course, multiple inheritance can be abused, but 'with great power comes great responsibility'. It would be really nice if there was a wrapper generator (i.e. macro) in the IDE for this sort of multiple inheritance workaround (or for the containment approach). I’m not a dogmatic C++ programmer, but I do enjoy having the option to use multiple inheritance. It saves you from having to ‘wrap’ all your method calls to the inner static. And, also you aren’t limited to using a static (i.e., your example could have had and used members in the interface). Of course, multiple inheritance can be abused, but ‘with great power comes great responsibility’.

It would be really nice if there was a wrapper generator (i.e. macro) in the IDE for this sort of multiple inheritance workaround (or for the containment approach).

]]> By: erik http://www.erik-rasmussen.com/blog/2006/10/23/multiple-inheritance-in-java/#comment-581 erik Mon, 19 Feb 2007 10:14:34 +0000 http://www.erik-rasmussen.com/blog/2006/10/23/multiple-inheritance-in-java/#comment-581 You're right. You're not the first person to note the flaw of that opening statement. No, it's not "one of its biggest flaws". However, the ability to inherit implementations from interfaces that I've demonstrated here is quite useful. You’re right. You’re not the first person to note the flaw of that opening statement. No, it’s not “one of its biggest flaws”.

However, the ability to inherit implementations from interfaces that I’ve demonstrated here is quite useful.

]]> By: fiath http://www.erik-rasmussen.com/blog/2006/10/23/multiple-inheritance-in-java/#comment-373 fiath Fri, 09 Feb 2007 09:00:59 +0000 http://www.erik-rasmussen.com/blog/2006/10/23/multiple-inheritance-in-java/#comment-373 "The lack of multiple [class] inheritance in Java is often considered one of its biggest flaws." Is that really true? I'm genuinely interested: Where did you get this from? Perhaps being around a load of hardened C++ programmers? ;) In 10 years of Java development, I have never needed multiple class inheritance that I couldn't otherwise represent using multiple interface inheritance and a few utility methods. I actually consider the concept horrible, and I'm glad Java doesn't have it. I think that the lack of multiple class inheritance in Java has saved a lot of people a lot of pain. Inheritance taken to far is bad (note: I am not saying inheritance is bad, but it is easily abused), multiple class inheritance would make that even worse. Even so, your ideas are interesting all the same :) “The lack of multiple [class] inheritance in Java is often considered one of its biggest flaws.”

Is that really true? I’m genuinely interested: Where did you get this from? Perhaps being around a load of hardened C++ programmers? ;)

In 10 years of Java development, I have never needed multiple class inheritance that I couldn’t otherwise represent using multiple interface inheritance and a few utility methods. I actually consider the concept horrible, and I’m glad Java doesn’t have it. I think that the lack of multiple class inheritance in Java has saved a lot of people a lot of pain. Inheritance taken to far is bad (note: I am not saying inheritance is bad, but it is easily abused), multiple class inheritance would make that even worse.

Even so, your ideas are interesting all the same :)

]]>