Java Multiple Inheritance

by

You could create interfaces for animal classes (class in the biological meaning), such as public interface Equidae for horses and public interface Avialae for birds (I’m no biologist, so the terms may be wrong).

Then you can still create a 

public class Bird implements Avialae {
}

and 

public class Horse implements Equidae {}

and also

public class Pegasus implements Avialae, Equidae {}

Adding from the comments:

In order to reduce duplicate code, you could create an abstract class that contains most of the common code of the animals you want to implement.

public abstract class AbstractHorse implements Equidae {}

public class Horse extends AbstractHorse {}

public class Pegasus extends AbstractHorse implements Avialae {}

Update

I’d like to add one more detail. As Brian remarks, this is something the OP already knew.

However, I want to emphasize, that I suggest to bypass the “multi-inheritance” problem with interfaces and that I don’t recommend to use interfaces that represent already a concrete type (such as Bird) but more a behavior (others refer to duck-typing, which is good, too, but I mean just: the biological class of birds, Avialae). I also don’t recommend to use interface names starting with a capital ‘I’, such as IBird, which just tells nothing about why you need an interface. That’s the difference to the question: construct the inheritance hierarchy using interfaces, use abstract classes when useful, implement concrete classes where needed and use delegation if appropriate.

More Related Contents:

  1. Multiple Inheritance in java
  2. Why to use Interfaces, Multiple Inheritance vs Interfaces, Benefits of Interfaces?
  3. How much interfaces a class file can implement [closed]
  4. Why we have access to A class methods only.Why overriding methods cannot be more restrictive? [closed]
  5. How do i get an object from another class in java
  6. What is the impact of declaring a method as final?
  7. Java polymorphism error? [closed]
  8. Method Overloading for null argument
  9. Are getters and setters poor design? Contradictory advice seen [duplicate]
  10. Can we instantiate an abstract class?
  11. “Program to an interface”. What does it mean? [duplicate]
  12. Using the “final” modifier whenever applicable in Java [closed]
  13. How to wire one pane to another
  14. Aggregation versus Composition [closed]
  15. Why doesn’t Java Map extend Collection?
  16. Encapsulation vs Abstraction?
  17. What is the point of setters and getters in java? [duplicate]
  18. What is the difference between identity and equality in OOP?
  19. Do/can abstract classes replace interfaces? [duplicate]
  20. Sending messages between two JPanel objects
  21. Static Binding and Dynamic Binding
  22. Difference Between Object Type and Reference Type
  23. Should you always Code To Interfaces In Java [closed]
  24. Access subclass fields from a base class in Java
  25. Are defaults in JDK 8 a form of multiple inheritance in Java?
  26. interface as a method parameter in Java
  27. Should methods that throw RuntimeException indicate it in method signature?
  28. Anonymous vs named inner classes? – best practices?
  29. Why are interfaces preferred to abstract classes?
  30. Methods With Same Name as Constructor – Why?

Leave a Comment