11.1 — Introduction to inheritance

In the last chapter, we discussed object composition, where complex classes are constructed from simpler classes and types. Object composition is perfect for building new objects that have a “has-a” relationship with their parts. However, object composition is just one of the two major ways that C++ lets you construct complex classes. The second way is through inheritance, which models an “is-a” relationship between two objects.

Unlike object composition, which involves creating new objects by combining and connecting other objects, inheritance involves creating new objects by directly acquiring the attributes and behaviors of other objects and then extending or specializing them. Like object composition, inheritance is everywhere in real life. When you were conceived, you inherited your parents genes, and acquired physical attributes from both of them -- but then you added your own personality on top. Technological products (computers, cell phones, etc…) inherit features from their predecessors (often used for backwards compatibility). For example, the Intel Pentium processor inherited many of the features defined by the Intel 486 processor, which itself inherited features from earlier processors. C++ inherited many features from C, the language upon which it is based, and C inherited many of its features from the programming languages that came before it.

Consider apples and bananas. Although apples and bananas are different fruits, both have in common that they are fruits. And because apples and bananas are fruits, simple logic tells us that anything that is true of fruits is also true of apples and bananas. For example, all fruits have a name, a color, and a size. Therefore, apples and bananas also have a name, a color, and a size. We can say that apples and bananas inherit (acquire) these all of the properties of fruit because they are fruit. We also know that fruit undergoes a ripening process, by which it becomes edible. Because apples and bananas are fruit, we also know that apples and bananas will inherit the behavior of ripening.

Put into a diagram, the relationship between apples, bananas, and fruit might look something like this:

This diagram defines a hierarchy.


A hierarchy is a diagram that shows how various objects are related. Most hierarchies either show a progression over time (386 -> 486 -> Pentium), or categorize things in a way that moves from general to specific (fruit -> apple -> red delicious). If you’ve ever taken biology, the famous domain, kingdom, phylum, class, order, family, genus, and species ordering defines a hierarchy (from general to specific).

Here’s another example of a hierarchy: a square is a rectangle, which is a quadrilateral, which is a shape. A right triangle is a triangle, which is also a shape. Put into a hierarchy diagram, that would look like this:

This diagram goes from general (top) to specific (bottom), with each item in the hierarchy inheriting the properties and behaviors of the item above it.

A look ahead

In this chapter, we’ll explore the basics of how inheritance works in C++.

Next chapter, we’ll explore how inheritance enables polymorphism (one of object-oriented programming’s big buzzwords) through virtual functions.

As we progress, we’ll also talk about inheritance’s key benefits, as well as some of the downsides.

11.2 -- Basic inheritance in C++
10.x -- Chapter 10 comprehensive quiz

12 comments to 11.1 — Introduction to inheritance

  • Omri

    By *atributes* in: "…Note that although children often redefine the attributes they inherit…", do you mean:
    a. member variables
    b. member functions
    c. both
    d. anything else?
    I think the term *redefinition* is new here and perhaps not fully clear.
    For variables, is it like reusing a name of a variable in a "contained" code block thus shadowing, within the block, its very existence outside the block?
    Have we ever redefined functions other than overloading them?

    • Alex

      Agree with your point of confusion. I’ve removed the term redefinition, and moved some of the C++ specific conversation into the next lesson.

      The basic idea is that if they wish, derived classes can override the value of member variables provided by the parent, or override the functionality of member functions provided by the parent. For functions, this is done via function overloading.

  • Alexander

    Wow, it’s been 8 years, 9 months and 24 days; and nobody pointed out the zuchinni (should be "zucchini" ofc) being misspelled?! 😮 Well then, let me be -that- guy. 😀

  • Sylvio

    This material is just amazing. My greatful thanks to the author!


    why inheritance?without inheritance cant i do what exactly inheritance does.

    • Alex

      Once you’ve read through the rest of this chapter and next, and I think you’ll see that inheritance gives you a lot of useful tools to do things that would be difficult or extremely redundant to do otherwise. Inheritance, properly used, can save you massive amounts of time and make your code significantly easier to maintain (by reducing the amount of redundant code you have to write and test).

  • prabodh

    Intro. abt inheritance is good

    but i have lots of confusion in inheritance like public,private and protected decleration (in inheritance)….please give me the simple trick so that i can understand very easily………

Leave a Comment

Put C++ code inside [code][/code] tags to use the syntax highlighter