In the previous lessons on inheritance, we’ve been making all of our data members public in order to simplify the examples. In this section, we’ll talk about the role of access specifiers in the inheritance process, as well as cover the different types of inheritance possible in C++.
To this point, you’ve seen the private and public access specifiers, which determine who can access the members of a class. As a quick refresher, public members can be accessed by anybody. Private members can only be accessed by member functions of the same class. Note that this means derived classes can not access private members!
class Base
{
private:
int m_nPrivate; // can only be accessed by Base member functions (not derived classes)
public:
int m_nPublic; // can be accessed by anybody
};
When dealing with inherited classes, things get a bit more complex.
First, there is a third access specifier that we have yet to talk about because it’s only useful in an inheritance context. The protected access specifier restricts access to member functions of the same class, or those of derived classes.
class Base
{
public:
int m_nPublic; // can be accessed by anybody
private:
int m_nPrivate; // can only be accessed by Base member functions (but not derived classes)
protected:
int m_nProtected; // can be accessed by Base member functions, or derived classes.
};
class Derived: public Base
{
public:
Derived()
{
// Derived's access to Base members is not influenced by the type of inheritance used,
// so the following is always true:
m_nPublic = 1; // allowed: can access public base members from derived class
m_nPrivate = 2; // not allowed: can not access private base members from derived class
m_nProtected = 3; // allowed: can access protected base members from derived class
}
};
int main()
{
Base cBase;
cBase.m_nPublic = 1; // allowed: can access public members from outside class
cBase.m_nPrivate = 2; // not allowed: can not access private members from outside class
cBase.m_nProtected = 3; // not allowed: can not access protected members from outside class
}
Second, when a derived class inherits from a base class, the access specifiers may change depending on the method of inheritance. There are three different ways for classes to inherit from other classes: public, private, and protected.
To do so, simply specify which type of access you want when choosing the class to inherit from:
// Inherit from Base publicly
class Pub: public Base
{
};
// Inherit from Base privately
class Pri: private Base
{
};
// Inherit from Base protectedly
class Pro: protected Base
{
};
class Def: Base // Defaults to private inheritance
{
};
If you do not choose an inheritance type, C++ defaults to private inheritance (just like members default to private access if you do not specify otherwise).
That gives us 9 combinations: 3 member access specifiers (public, private, and protected), and 3 inheritance types (public, private, and protected).
The rest of this section will be devoted to explaining the difference between these.
Before we get started, the following should be kept in mind as we step through the examples. There are three ways that members can be accessed:
- A class can always access it’s own members regardless of access specifier.
- The public accesses the members of a class based on the access specifiers of that class.
- A derived class accesses inherited members based on the access specifiers of its immediate parent. A derived class can always access it’s own members regardless of access specifier.
This may be a little confusing at first, but hopefully will become clearer as we step through the examples.
Public inheritance
Public inheritance is by far the most commonly used type of inheritance. In fact, very rarely will you use the other types of inheritance, so your primary focus should be on understanding this section. Fortunately, public inheritance is also the easiest to understand. When you inherit a base class publicly, all members keep their original access specifications. Private members stay private, protected members stay protected, and public members stay public.
class Base
{
public:
int m_nPublic;
private:
int m_nPrivate;
protected:
int m_nProtected;
};
class Pub: public Base
{
// Public inheritance means:
// m_nPublic stays public
// m_nPrivate stays private
// m_nProtected stays protected
Pub()
{
// The derived class always uses the immediate parent's class access specifications
// Thus, Pub uses Base's access specifiers
m_nPublic = 1; // okay: anybody can access public members
m_nPrivate = 2; // not okay: derived classes can't access private members in the base class!
m_nProtected = 3; // okay: derived classes can access protected members
}
};
int main()
{
// Outside access uses the access specifiers of the class being accessed.
// In this case, the access specifiers of cPub. Because Pub has inherited publicly from Base,
// no access specifiers have been changed.
Pub cPub;
cPub.m_nPublic = 1; // okay: anybody can access public members
cPub.m_nPrivate = 2; // not okay: can not access private members from outside class
cPub.m_nProtected = 3; // not okay: can not access protected members from outside class
}
This is fairly straightforward. The things worth noting are:
- Derived classes can not directly access private members of the base class.
- The protected access specifier allows derived classes to directly access members of the base class while not exposing those members to the public.
- The derived class uses access specifiers from the base class.
- The outside uses access specifiers from the derived class.
To summarize in table form:
| Base access specifier | Derived access specifier | Derived class access? | Public access? |
|---|---|---|---|
| Public | Public | Yes | Yes |
| Private | Private | No | No |
| Protected | Protected | Yes | No |
Private inheritance
With private inheritance, all members from the base class are inherited as private. This means private members stay private, and protected and public members become private.
Note that this does not affect that way that the derived class accesses members inherited from its parent! It only affects the code trying to access those members through the derived class.
class Base
{
public:
int m_nPublic;
private:
int m_nPrivate;
protected:
int m_nProtected;
};
class Pri: private Base
{
// Private inheritance means:
// m_nPublic becomes private
// m_nPrivate stays private
// m_nProtected becomes private
Pri()
{
// The derived class always uses the immediate parent's class access specifications
// Thus, Pub uses Base's access specifiers
m_nPublic = 1; // okay: anybody can access public members
m_nPrivate = 2; // not okay: derived classes can't access private members in the base class!
m_nProtected = 3; // okay: derived classes can access protected members
}
};
int main()
{
// Outside access uses the access specifiers of the class being accessed.
// Note that because Pri has inherited privately from Base,
// all members of Base have become private when access through Pri.
Pri cPri;
cPri.m_nPublic = 1; // not okay: m_nPublic is now a private member when accessed through Pri
cPri.m_nPrivate = 2; // not okay: can not access private members from outside class
cPri.m_nProtected = 3; // not okay: m_nProtected is now a private member when accessed through Pri
// However, we can still access Base members as normal through Base:
Base cBase;
cBase.m_nPublic = 1; // okay, m_nPublic is public
cBase.m_nPrivate = 2; // not okay, m_nPrivate is private
cBase.m_nProtected = 3; // not okay, m_nProtected is protected
}
To summarize in table form:
| Base access specifier | Derived access specifier | Derived class access? | Public access? |
|---|---|---|---|
| Public | Private | Yes | No |
| Private | Private | No | No |
| Protected | Private | Yes | No |
Protected inheritance
Protected inheritance is the last method of inheritance. It is almost never used, except in very particular cases. With protected inheritance, the public and protected members become protected, and private members stay private.
To summarize in table form:
| Base access specifier | Derived access specifier | Derived class access? | Public access? |
|---|---|---|---|
| Public | Protected | Yes | No |
| Private | Private | No | No |
| Protected | Protected | Yes | No |
Protected inheritance is similar to private inheritance. However, classes derived from the derived class still have access to the public and protected members directly. The public (stuff outside the class) does not.
Summary
The way that the access specifiers, inheritance types, and derived classes interact causes a lot of confusion. To try and clarify things as much as possible:
First, the base class sets it’s access specifiers. The base class can always access it’s own members. The access specifiers only affect whether outsiders and derived classes can access those members.
Second, derived classes have access to base class members based on the access specifiers of the immediate parent. The way a derived class accesses inherited members is not affected by the inheritance method used!
Finally, derived classes can change the access type of inherited members based on the inheritance method used. This does not affect the derived classes own members, which have their own access specifiers. It only affects whether outsiders and classes derived from the derived class can access those inherited members.
A final example:
class Base
{
public:
int m_nPublic;
private:
int m_nPrivate;
protected:
int m_nProtected;
};
Base can access it’s own members without restriction. The public can only access m_nPublic. Derived classes can access m_nPublic and m_nProtected.
class D2: private Base
{
public:
int m_nPublic2;
private:
int m_nPrivate2;
protected:
int m_nProtected2;
}
D2 can access it’s own members without restriction. D2 can access Base’s members based on Base’s access specifiers. Thus, it can access m_nPublic and m_nProtected, but not m_nPrivate. Because D2 inherited Base privately, m_nPublic, m_nPrivate, and m_nProtected are now private when accessed through D2. This means the public can not access any of these variables when using a D2 object, nor can any classes derived from D2.
class D3: public D2
{
public:
int m_nPublic3;
private:
int m_nPrivate3;
protected:
int m_nProtected3;
};
D3 can access it’s own members without restriction. D3 can access D2’s members based on D2’s access specifiers. Thus, D3 has access to m_nPublic2 and m_nProtected2, but not m_nPrivate2. D3 access to Base members is controlled by the access specifier of it’s immediate parent. This means D3 does not have access to any of Base’s members because they all became private when D2 inherited them.
11.6 — Adding, changing, and hiding members in a derived class
|
Index
|
11.4 — Constructors and initialization of derived classes
|
11.6 — Adding, changing, and hiding members in a derived class
Index
11.4 — Constructors and initialization of derived classes
very comprehensive tutorial.. kudos to you!!
Amazing Tutorials. No more words.
I have been working as Software engineer of Real Time Embedded for 7 years and I discovered that there is many things I never knew.
Thank you
Wael
Very clear, thanks a lot!
In the first example under the title “Public inheritance” the Pub constructor should be public. Apart from that, great tutorial (judging from what i’ve seen until now).
Ben
Good catch, the code will not compile because the examples clearly state “not ok …”, which in case will give compiler errors. If those examples are commented out, it is true, you will still get an error since the Pub default constructor is private by default.
Hi Alex,
I think the following table may help to clarify the access mechanisms for the various cases.
By sub_derived I mean a class derived from a class already derived from a base class. The subtly
of the difference between protected and private inheritance only comes into play at that level.
The table assumes your three base class members with differing access levels.
The inheritance access is applied when the derived class is created from the base class. The
inheritance of the sub-derived class from the derived class is public.
So we have:
class Base
{
public:
int m_nPublic;
private:
int m_nPrivate;
protected:
int m_nProtected;
}
class derived : xxx Base // xxx is public, protected or private
{
}
class sub_derived : public derived
{
}
xxx is public
derived sub_derived public
m_nPrivate3 No No No
m_nProtected3 Yes Yes No
m_nPublic3 Yes Yes Yes
xxx is protected
derived sub_derived public
m_nPrivate3 No No No
m_nProtected3 Yes Yes No
m_nPublic3 Yes Yes No
xxx is private
derived sub_derived public
m_nPrivate3 No No No
m_nProtected3 Yes No No
m_nPublic3 Yes No No
Oh dear, the tags didn’t work and it’s squashed my tables! Grrr.
Sorry it squashed your table. As the note says just below the comment box:
Other tags get stripped out, including tables. This is done for the protection of the readers and the integrity of the site — malformed tables can easily make all comments that follow completely unreadable.
To bad the tables didn’t work. Thanks for the added summary. A very nice compliment to the tutorial.
so, private and protected inheritance only differ in classes that are derived more than one time (multiple inheritance), it’s that right?
I suppose you could look at it that way. Really the derived class does differ, since members will have different access specifiers. However, as you imply, since private and protected have the same access restrictions within a class, there’s no practical difference until you derive the class again.
Just so you know, the term multiple inheritance should not be used when referring to a class that has been derived multiple times. It has a different meaning: a class that is derived from multiple parents simultaneously. We cover multiple inheritance in a few more lessons.
It’s very useful doc for those who are beginner in c++.
Excellent article…
Thanks,
Purushothman J
excellent tutorial…
Very informative… some stuff i didnt know…thnaks a lot
very good example
here u willget complete view of the exact inheritance is
very nice example
I have neve seen such a clear definitions and examples before. Thanks Alex!
Really amazing tutorial… I got many-things new here…
thank you very much…..
Very good explanation done. Thanks.
Thanx a tonne..Beautiful Tutorial..Finally understood what all class specifiers are after 3 yeras of graduation??
thanks it made the topic more clear
migmar dolma
Great tutorial. Thanks.