Multiple Inheritance confusion
Hi,
I am having a confusion.
Java specification says that Java does not allow multiple inheritance; but any class in Java is by default inherited from Object class. Now if any class by default extends from Object then how does it allows other class to be inherited.
Example
public class A {
A() {}
public class B extends A {
B(){}
}The above code does not give any error.
here the class B by default becomes the subclass of class Object then how did it allowed me to extend from class A.
Can any one solve my confusion.
just to reiterate...
multiple inheritance eg,
class A{}
class B{}
class C extends A, B{}
multi-level eg,
class A{}
class B extends A{}
class C extends B{}
//java does not allow multiple inheritance
I hope the idea is clear to you now.
Edited by: yazee on Oct 25, 2007 11:33 AM
Similar Messages
-
Hi all,
I am confused by the java statement that "By using interface we can achieve multiple inheritance bcoz java doesn't support Multiple inheritance".
Yes.Ok java doent support Multiple inheritance. Now we know that inheritance means that "one object acquires the property of another object".
So how can it is possible achieve Multiple inheritance by interface.
Interface that contains just undefined methods like below code.
interface Member1
public void eye();
public void nose();
public void mouth();
interface Member2 extends member1
public void neck();
public void hand();
public void stomach();
interface Member3 extends Member1,Member2
public void leg();
class Man implements Member3
public man()
Member3 ref=new Man();
// Here Implements all 7 methods.
Is the above code defines multiple Inheitance?
undefined methods are eye,nose,mouth,neck,handand stomach are fall in Interface Member3 .Yes. But Inheritance means that one object acquires the property of another object.Property means that code and data.
In here, there is no code just declarations of method which is not to be a code .
So How can we say interface achieve multiple inheritance.
Please any one explain and clear my doubt with simple example.
with cheers,
G.GandhiRaj.Multiple inheritance is about aquiring both behavior and attributes from two or more sources. A lot of times, this "is a" relationship is confused with "has a" relationships.
For example, a Book "has a" Page. A Book "is a" Publication. So multiple inheretance in this instance would come from stating that a Book "is a" Publication and "is a" PaperProduct. In this example, you could redesign your model and state that a PaperProduct inherits from Publication. However, a Book doesn't have to be limited to being a PaperProduct, it can also be an ElectronicProduct, thus inhereting attributes and behaviors from this new class as well. In essence, the Book can exist in two forms simulataneously (as many actually do). So you still have the need for multiple inheritance - perhaps.
Interfaces define the behavioral aspects of multiple inheritance. You loose the aquisition of attributes from base classes. In many cases this is acceptable. For the first time I recently found a true need for multiple inheritance in one fo my Java apps. Some would say that my data model is poorly designed then. So I tried restructuring the model and that solve the problem.
It is probably a good idea to completely understand your data model from many dimensions first before resorting to the copying of attributes like I almost did. Don't be locked into a design too quickly. Be willing to change your mind and you will probably find a solution that works. -
No Calrity on Multiple Inheritance Concept Of Java..!
In SCJP Book by "karty serie " .
In Java
a subclass of class Object, (except of course class Object itself). In other words, every
class you'll ever use or ever write will inherit from class Object. You'll always have
an equals method, a clone method, notify, wait, and others, available to use.
Whenever you create a class, you automatically inherit all of class Object's methods.
A class cannot extend more than one class. That means one parent per class. A
class can have multiple ancestors, however, since class B could extend class A, and
class C could extend class B, and so on. So any given class might have multiple
classes up its inheritance tree, but that's not the same as saying a class directly
extends two classes.
class PlayerPiece extends GameShape, Animatable { // NO!
// more code
If the above code is invalid, is it legal to write the code like ...
class PlayerPiece extends GameShape, Object { // NO!
// more code
Thanks In Advance
KiranI think I can help straighten out what is confusing you.
Let's say you have a class B that extends class A, and a class C that extends class B.
Then class C implicitly extends class A, but java does not allow you to make that explicit.
So, yes, in a way, class C does subtype both class A and B, but it only directly subclasses class B. The subtyping of class A is implicit.
The following should demonstrate some patterns that should help clear things up:
class A { }
// This automatically is a subclass of Object,
// you don't need to specify that.
// or
class A extends Object { }
// This is legal, but not necessary, since a class
// that doesn't extend anything else implicitly extends Object
class B extends A { }
// This directly subclasses class A,
// and implicitly subtypes Object
// but
class B extends A, Object { }
// This is NOT legal in java, and will not compile,
// even though the previous code would
// make class B a subtype of Object
class C extends A { }
// Again, a direct subclass of A,
// and indirect subclass of Object
class D extends B, C { }
// This is NOT legal in java, and is what people
// usually mean when they say that multiple
// inheritance is prohibited. In this case, you
// are attempting to subclass two different
// classes, where one is *not* a subtype of
// another. There is no work around to make
// this happen in java, but you can use interfaces
// and composition to get a similar effect with a
// bit of glue code to hook things together.
// For example:
interface X {
public void doX();
class XImpl implements X {
public void doX() {
// do something
interface Y {
public void doY();
class YImpl implements Y {
public void doY() {
// do something else
class Z implements X, Y {
private X x = new XImpl();
private Y y = new YImpl();
public void doX() {
x.doX();
public void doY() {
y.doY();
// This is basically what goes on behind the scenes
// in languages like C++ that do support MI -
Why java does not support multiple inheritance ???
Hai friends ..iam new to java .. i have doubt ..plz help me
Why java does not support multiple inheritance ???The reasons for omitting multiple inheritance from the Java language mostly stem from the "simple, object oriented, and familiar" goal.
To understand multiple inheritance, the learner needs some level of expertise like virtual derivations etc in c++. Multiple inheritance will allow method duplication, and throws the learner into confusion which method might be called by the compiler in which scenario at run time.
Even though this answer seems to be funny, this is the actual reason why java omitted multiple inheritance of classes.
But java support multiple inheritance of interfaces. Multiple interface inheritance allows an object to inherit many different method signatures with the caveat that the inheriting object must implement those inherited methods. -
How does Java achieve multiple inheritance using interfaces
Java does not allow multiple inheritance through classes as classes might contain methods with same names. what happens if a class implements two interfaces with same method names?
I am really confused abt this? Can anybody help me out?
Message was edited by:
vijkrisyes to avoid the ambiguous functions which can result due to multiple inheritance of classes like in c++ , java doesn't have this through classes. But if you have same method (both return type and parameter) then java doesn't bother and it won't complain as ultimately only one implementation is possible in deriving class even though method declalaration is there in both the interfaces. If return type changes then it won't compile as it can't overide the both methods as they have same name and different return types. thats why inside interfaces they restricted the implementation of methods so that it can work fine in ambiguous scenarios.
-
More about multiple inheritance
OK, you can solve problems where multiple inheritance is needed by using interfaces. But im facing a problem where it cant help me. Im constructing a system where there are componentes that need to extend JTextField as well Observable. I dont have interfaces above it in the hierarchy to substitute multiple inheritance. What can I do?
When you have a scenario that you have to use two (or more) third party classes, and need to inherit from both, how do interfaces can help? If ate least I had multiple inheritance from classes...<< Begin Rant >>
I have seen more inherited code that is terribly designed because multiple inheritence was available.
The example provided is a perfect example of this: At first blush, it seems easy to combine the UI and data components by combining Observable and JTextArea. If you were able to do this, the person inheriting your code in 3 years will curse your name.
Nothing pisses me off more (well, I'm sure there are other things, but...) than attempting to debug C++ source code and finding that function calls are being made to multiple super classes.
Here's a fun one: try adding an innocuous method getInfo() to a class you've inherited, only to find that someone uses getInfo() in one of the super-classes, and it has been declared as 'friend' because the design is piss poor and it was the only way they could make the function available. Now, I have to go on a goose chase searching for all the places in the entire type hierarchy that getInfo() is used and change the code to explicitly call the other base class.
It gets to the point where its easier to name it getInfo2() (like that's good design) and get on with things.
MI is evil, evil, evil in any environment where you are trying to have code re-use and multiple teams.
I find that most programmers who insist that multiple inheritence is a good thing just don't know how to use the Composite design pattern.
Sun's decision to not support MI in Java is a sound one: the result is code that can be easily read and understood.
<< End Rant >>
Whew... I feel much better having said that...
- K -
Problems of no multiple inheritance.
I have created two classes RECTANGLE with attributes Length and Height and PLANERECTANGLE, with various attributes required to specify the rectangle's center, an attribute that can be checked to see if it is inside an instance of rectangele. However, i am finding this following requirement difficult to understand.
In Question 5, we specified PlaneRectangle as a subclass of Rectangle. Suppose that we wanted the following generic behaviour to be implemented in a number of different �kinds of� shapes: being able to move a shape, check if a point is inside a shape, and check if another shape lies completely inside a specified instance of some shape. Java will not let us do this using multiple inheritance. How else could we specify this? Rewrite the Java code to illustrate use of this different method.
Thanks - Mark Costello.The answer would be an interface
public interface Shape
public void moveShape();
public boolean containsPoint(int x, int y);
public boolean containsShape(Shape s);
Every shape class would then implement this interface:
public class Circle implements Shape
... and would need to implement those methods that
were specified (but not implemented) in the interface. -
Alternative for multiple inheritance (AbstractQueue and AbstractList)
Hello all,
What is the best alternative for multiple inheritance? I want to make a list, which supports queue operations. Both AbstractQueue en AbstractList are useful, so I would like to use them both, instead of implementing the methods myself or copying the code.
thanksDo you mean you want a class just like LinkedList?
Why don't you look at the code for LinkedList. Perhaps you could even use it.
Most Queue methods have trivial implmentations using a List.
From the source for LinkedList
public class LinkedList<E>
extends AbstractSequentialList<E>
implements List<E>, Queue<E>, Cloneable, java.io.Serializable -
How java support multiple inheritance by the use of interface.
As per my understanding, Interface is just having the signatures of the methods not the implementation.
So How java support multiple inheritance by the use of interface?
Answer 1: we can institate interface reference by its implemented
class.
����� interface inf...
����� class aa implements inf..
����� class bb implements inf....
Now, inf i = new aa();
inf i = new bb();
Answer 2: We can extends as many interface as we want in the
single
interface.
i.e. interface infFirst....
interface infSecond....
interface infThird....
Now ,
interface ingMulti extends infFrist, infThird...
By above two answers its not prity clear as per the multiple inheritance in C or C++.
i.e.
class first{
method abc();....}
class second{
method bbc()......}
class multi::first::second{
we can call to abc();.....as well as bbc();
-Please give your important suggstion on the same.(Hope I explain it well.)
-JeffThe keyword implement is used only for interfaces not
for abstract class. If i am wrong correct me.I believe your right, but I will double check.
As for the multiple inheritence think about the following code:
class Animal {
// Animal generic stuff in this class
interface Eat {
// Generic stuff that models eating behavior
interface Runs {
// generic methods that model running behavior
public class Horse extends Animal implements Eat, Runs {
// Stuff specific to a horse
}The Animal class is generic but has stuff in it common to all animals.
The Eat interface models behavior that is generic to eating, all living things have to eat something to survive. Herbavore are different from carnivores.
The Runs interface models generic behavior to running, such as speed. A cheeta definately runs faster than a human.
This brings us to the Horse class. It extends the Animal class because it "is-a" animal, and it implements the eat and runs interface because they are behaviors a horse has.
I hope that helps.
Extending an abstract class is the same as extending a regular class with the exception you MUST override all abstract methods in the abstract class. Thats not too difficult but I believe when designing classes, designing an abstract can be more diffecult than modeling the base class, and generic behaviors in interfaces. JMO.
JJ -
Multiple inheritance in tagging interface? Is it possible?
I saw a code somewhere that goes like this:
public interface Node extends Serializable, Clonable
...Is it possible? I know that Java doesn't allow multiple inheritance and that Serializable and Clonable are tagging interfaces where no method must be implemented by the programmer.KamenRiderZX wrote:
I know that Java doesn't allow multiple inheritanceMore exactly: Java doesn't allow multiple inheritance of implementations. Inheriting multiple interfaces ("implements" for classes, "extends" for interfaces) is fine 'though. -
Question about multiple inheritance
Why does java not support multiple inheritance, but also give you the ability to use interfaces?
I've done a quick search on here which turned up the same thing as the books on java I've read - they tell me that java doesn't support multiple inheritance, and that it supports interfaces, but not why.
And from what I can see, the between multiple inheritance and single inheritance + interfaces make them seem almost equivalent, especially when you consider abstract classes. So why did the java designers make this decision?
Edit: Just to say I've never programmed in an OO language that supports multiple inheritance, so I've never had to deal with it. Also, single inheritance has never crippled any of my designs (not that there have been that many), I'm not whingeing, just asking.
Message was edited by:
DrossWhy does java not support multiple
inheritance, but also give you the ability to use
interfaces?It does support MI, just not MI of Implementation.
why.
class Beasty { }
class Horse extend Beasty {
public void gallop() { System.out.println( "horse" ); }
class Donkey extend Beasty {
public void gallop() { System.out.println( "donkey" ); }
class Mule extend House, Donkey {
Mule mule = new Mule();
mule.gallop();what would this print out.
MI of implementation makes life harder, but adds very little to the party. So why add it? -
Hello,
I have been programming Java for last year,
evolved in quite some skills with it, and
really think it is great...
However, I was shocked to find out that there
is no multiple inheritance feature.
I know it is rare, and my case proves it
(1 year now, I never needed it)
HOWEVER, when one needs multiple inheritance,
then they really do need it.
I have interfaces which I would like implemented
in their respective class (ie ISomething be
implemented in CSomething), then some classes
I need to implement many of those interfaces...
Now I am forced to have those classes extend
multiple interfaces, and duplicate the interface
implementation code inside each of them.
I dont mind a little bit of copy/paste, nor
do I care about the compiled classes being
slightly bigger, BUT the problem is that
when I need to change some behaviour in those
interfaces, in the near (or far) future, I will
have their implementation scattered in many
classes... This is dangerously error prone and
not proffesional at all... And I do not think
that including multiple inheritance in the language
could be more error prone than this...
I think the Java team does a 100% perfect brilliant
job, but at this specific point, they "over-tried"
to "protect" the programmers from themselves...
Well, thats all,
I think some next version of Java should support
multiple inheritance. And the Java "warning" could be :
"if you havent missed it till now, then you probably
do not need anyway, so do not bother using it just
because it exists"
Thanks for reading my thoughts,
DimitrisPersonally I never need multiple inheritance of code and I try to avoid inheritance of code whenever possible. A common mistake in OO is too use inheritance as a way of reusing code. Code reuse is much easier, cleaner and more powerful by using composition instead. Only use inheritance for polymorhism (to use multiple implementations for the same interface). An example:
interface A {
void ma();
void maa();
interface B {
void mb();
class C implements A, B {
private A a;
private A c;
private B b;
public void ma() {
a.ma();
public void maa() {
c.maa();
public void mb() {
b.mb();
}This is much more powerful than code reuse through inheritance. In this example I use one method from 'a' and one method from 'c' when I implement interface A. I can change the value of 'a', 'b' and 'c' during runtime, and I dont have to reuse all the code in 'a' and 'b', I can select which code to reuse. This is the power of composition and interfaces. Note that I only access 'a', 'b' and 'c' through the interfaces A and B, never directly through their implementations.
I would recommend you to look at your design and start to think about interfaces and inheritance, not about code reuse though inheritance. -
INF Looking for means to dialog C#-Dev team about multiple inheritance.
Please help.
I really need multiple inheritance with C#. Is there any forum/means to have a dialog with the dev's for C# about this? The amount of extra work and maintenance costs of not having multiple inheritance has been a big problem, but lately, it has really become
a burden for not having. The maintainability and reuse-ability of code is drastically reduced without it.Btw, I think that this has been discussed
many times before. Almost once or twice each year since .NET is released (that's 12 years by now).
I don't think you can make them allow this feature as tons of example trying to convince them this is needed has been proved not necessary to use multiple inheritance by them.
Many of the discussions ends with something like "Java also does not support multiple inheritance but there isn't seems to be a problem for them". Maybe you can get more luck to convince Oracle to include MI in Java first.
Btw, I found it hard to believe you need Multiple Implementation Inheritance to... improve maintainability of code? WTF??? I think Multiple Implementation Inheritance has it own place in the hall of fame for the bugs it caused in languages that supports
it, even in C++. -
Coding isn't that hard actually. The hard part is to write code that makes sense, is readable and understandable. So I want to get a better developer and create some solid architecture.
So I want to do create an architecture for NPCs in a video-game. It is a Realtime
Strategy game like Starcraft, Age of Empires, Command & Conquers, etc etc.. So I'll have different kinds of NPCs. A NPC can have one to many abilities (methods) of these: Build(), Farm() and Attack().
Examples:
Worker can Build() and Farm()
Warrior can Attack()
Citizen can Build(), Farm() and Attack()
Fisherman can Farm() and Attack()
I hope everything is clear so far.
So now I do have my NPC Types and their abilities. But lets come to the technical / programmatical aspect.
What would be a good programmatic architecture for my different kinds of NPCs?
Okay I could have a base class. Actually I think this is a good way to stick with the DRY principle.
So I can have methods like WalkTo(x,y) in
my base class since every NPC will be able to move. But now lets come to the real problem. Where do I implement my abilities? (remember: Build(), Farm() and Attack())
Since the abilities will consists of the same logic it would be annoying / break DRY principle to implement them for each NPC (Worker,Warrior, ..).
Okay I could implement the abilities within the base class. This would require some kind of logic that verifies if a NPC can use ability X. IsBuilder, CanBuild,
.. I think it is clear what I want to express.
But I don't feel very well with this idea. This sounds like a bloated base class with too much functionality.
I do use C# as programming language. So multiple inheritance isn't an opinion here. Means: Having extra base classes like Fisherman
: Farmer, Attacker won't work.Hi
PandoraElite,
You can inherit from multiple interfaces (and use explicit interface implementation), but not from classes in C#. You can almost simulate it:
In C# we don't support multiple inheritance
http://blogs.msdn.com/b/csharpfaq/archive/2004/03/07/why-doesn-t-c-support-multiple-inheritance.aspx
What would be a good programmatic architecture for my different kinds of NPCs?
In your scenario, we can define some interface ,An interface contains only the signatures of methods, properties, events or indexers. A class or struct that implements the interface must implement the members of the interface that are specified
in the interface definition.
How to use? Please refer to the following article.
http://www.codeproject.com/Articles/18743/Interfaces-in-C-For-Beginners
Best of luck!
Kristin
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Why it is sometimes said that interfaces provide a form of multiple inheritance?
Do you agree that interfaces can provide multiple inheritance? Explain.
Some people say that Java does not support multiple inheritance, and others: a class can implement more than 1 interface. Isn't that multiple inheritance?
Thanks>
Some people say that Java does not support multiple
inheritance, and others: a class can implement more
than 1 interface. Isn't that multiple inheritance?Sort of, but you don't inherit any implementation from an interface.
Maybe you are looking for
-
I have a file that is 4,036kb and it needs to be less than 3MB. I read some articles about file optimizer; but I cannot find any way to access it nor do I know if it is possible. Can someone please help???
-
Can we have datepicker for interactve report using date_popup2
Hello All, I am trying to implement a text field with date picker in interactive report using apex_items in report region in oracle apex- 4.0.2. and it returned a text item with datepicker calender icon for the first row. the rest of the rows just re
-
Hi BW Gurus, I tried to load the FIGL line item extractor - FI_GL_14 and it failed after 2 days. Due to memory and also system resiurces. I plan to do the following. 1.Create a infopackage for each fiscal period and do a full load. 2.After all the lo
-
just installed firefox 32.0 on windows 7 and windows xp and got a new plugin check bug - comes up with "Adobe Acrobat NPAPI Plug-inAdobe Acrobat NPAPI Plug-in" as vulnerable but when you hit the red button the page just navigates to itself have also
-
Hi I have latest Airport Extreme with 2TB hard disk (Time Capsule). I have working private network after latest firmware update (7.7.2 here) except my guest network. I have tried to setup the guest network as open network and WPA/WPA2 network with pa