As title says, the meaning of both eludes me.
- possible duplicate of Difference between Inheritance and Compositionnawfal– nawfal2013-10-03 10:45:46 +00:00Commented Oct 3, 2013 at 10:45
- Watch this talk and you will understand: youtu.be/29MAL8pJImQ?t=1380EpicPandaForce– EpicPandaForce2020-06-18 10:09:08 +00:00Commented Jun 18, 2020 at 10:09
- You inherited some attributes from you parents. You are composed of many other attributes also.anwar– anwar2024-06-02 15:15:41 +00:00Commented Jun 2, 2024 at 15:15
8 Answers
Inheritance expresses an is-a relationship, while composition expresses a has-a relationship between the two classes.
An example for composition is a polygon. It has an ordered sequence of Points. In C++ terms:
struct Polygon { std::vector<Point> points; }; While an logic_error is a exception:
struct logic_error : public exception { }; 4 Comments
:)As pmr pointed out, inheritence is a is-a relationship, composition is a has-a relationship.
Composition is usually used for wrapping classes and to express relationships between classes that contain one another.
Inheritance is used for polymorphism, where you have a base class and you want to extend or change its functionality.
Comments
Inheritance means inheriting something from a parent. For example, you may inherit your mother's eyes or inherit your father's build.
It means deriving properties, characteristics and behaviors from a parent class. So you can parent.walk(), parent.sleep(), parent.sleep() or whatever.
Containership or maybe composition is a bit hard to explain.
Or maybe a car has a brake. The car is composed of a brake. But the brake isn't inheriting from a brake..different concepts. I know very weird explanation..but that's how much I can do I guess.
Let's look at this code:
class Parent { public : void sleep() ; void eat() ; void walk() ; string eyeColor; int height ; }; class Child: public Parent { } So the Child class can inherit the functions and attributes of the Parent but of course it may have the eye color of the mother or father.. Even if the childs' attributes are different it can still do whatever the Parent can do.
Now composition is another thing. A Child can have a toy or a Parent can have a child. So I could do:
class Toy { string model ; }; class Child { Toy transformersToy ; }; So the Child has the transformers toy now.. but does Child inherit the transformersToy.model attribute? No, because it isn't inheriting.
1 Comment
One main point I see is the ownership on the objects. Inheritance doesnt own/give any thing it just gives the characteristics of the base class. While Composition gives the owner ship to the created object.
In the first example polygon has a vector of points. So polygon owns/contains points in it. While in inheritance you can have/use/extend the existing characteristics of the base class.
Comments
In aspect of memory management there is no difference, the Base class instance comes in the beginning of the DER class, so their addresses are equal. The difference is the type of relationship between them: -in inheritance we have "is-a" -in composition we have "has-a" as mentioned before.