Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

C++ multiple inheritance order

I'm trying to understand the affect of inheritance order in C++.. I looked online, but I couldn't find a clear and sufficient answer...

So, for the sake of the question, assume there are 2 classes: class B and class C.

Now, define:

class A1 : public B, public C{ ... }; class A2 : public C, public B{ ... }; 

What is the difference between A1 and A2?

Thanks a lot!

like image 892
TCS Avatar asked Jun 26 '13 19:06

TCS


People also ask

Does order matter in multiple inheritance?

The order of derivation is not significant except as specified by the semantics of initialization by constructor (12.6. 2), cleanup (12.4), and storage layout (9.2, 11.1). Constructors are called in the order you write them down (first base class in the list is constructed first) (§12.6.

Does C have multiple inheritance?

In Multiple inheritance, one class can have more than one superclass and inherit features from all its parent classes. As shown in the below diagram, class C inherits the features of class A and B. But C# does not support multiple class inheritance.

Does inheritance sequencing order matter?

The order of construction depends on the sequence of inheritance. Initialization order doesn't matter.

How does multiple inheritance work in CPP?

Multiple Inheritance in C++Multiple inheritance occurs when a class inherits from more than one base class. So the class can inherit features from multiple base classes using multiple inheritance. This is an important feature of object oriented programming languages such as C++.


2 Answers

The C++11 Standard says (§10.1) [class.mi]:

The order of derivation is not significant except as specified by the semantics of initialization by constructor (12.6.2), cleanup (12.4), and storage layout (9.2, 11.1).

The three referenced paragraphs reveal that

  • Constructors are called in the order you write them down (first base class in the list is constructed first) (§12.6.2.10). Different rules apply to virtual base classes which are always constructed from the most-derived class before any direct base classes.
  • Destructors are called in the inverse order of construction (first base class in the list is destructed last)
  • Storage layout is unspecified. You must not make any assumptions about the class layout in memory. The only exception are so called standard-layout classes (§9), which is basically a C-style struct. But since those are not allowed to have more than one class with non-static members in the class hierarchy, the question does not really apply here.

Note that the memory layout can be important. For example, if an external library makes naive C-style casts that assume that the part of the object it's interested in is at the beginning, it can lead to run time errors that are hard to debug.

like image 151
ComicSansMS Avatar answered Sep 25 '22 21:09

ComicSansMS


The order of derivation is relevant only to determine the order of default initialization by constructors and cleanup by destructors.

The order of derivation is not significant except as specified by the semantics of initialization by constructor (12.6.2), cleanup (12.4), and storage layout (9.2, 11.1). — end note ]" (§10.1/2)

From IBM's C++ documentation: Multiple inheritance

like image 27
Haagenti Avatar answered Sep 24 '22 21:09

Haagenti