为什么我们在 C++ 中实际上需要 Private 或 Protected 继承?

Why do we actually need Private or Protected inheritance in C++?(为什么我们在 C++ 中实际上需要 Private 或 Protected 继承?)
本文介绍了为什么我们在 C++ 中实际上需要 Private 或 Protected 继承?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着跟版网的小编来一起学习吧!

问题描述

在 C++ 中,我想不出我想从一个继承私有/保护的情况基类:

In C++, I can't think of a case in which I would like to inherit private/protected from a base class:

class Base;
class Derived1 : private Base;
class Derived2 : protected Base;

真的有用吗?

推荐答案

当您想要访问基类的某些成员,但又不想在类接口中公开它们时,它很有用.私有继承也可以看作是某种组合:C++ faq-lite 给出下面的例子来说明这个语句

It is useful when you want to have access to some members of the base class, but without exposing them in your class interface. Private inheritance can also be seen as some kind of composition: the C++ faq-lite gives the following example to illustrate this statement

class Engine {
 public:
   Engine(int numCylinders);
   void start();                 // Starts this Engine
};

class Car {
  public:
    Car() : e_(8) { }             // Initializes this Car with 8 cylinders
    void start() { e_.start(); }  // Start this Car by starting its Engine
  private:
    Engine e_;                    // Car has-a Engine
};

为了获得相同的语义,您也可以将汽车类编写如下:

To obtain the same semantic, you could also write the car Class as follow:

class Car : private Engine {    // Car has-a Engine
 public:
   Car() : Engine(8) { }         // Initializes this Car with 8 cylinders
   using Engine::start;          // Start this Car by starting its Engine
}; 

然而,这种做法有几个缺点:

However, this way of doing has several disadvantages:

  • 你的意图不太清楚
  • 它可能导致滥用多重继承
  • 它破坏了 Engine 类的封装,因为您可以访问其受保护的成员
  • 您可以覆盖引擎虚拟方法,如果您的目标是一个简单的组合,这是您不想要的

这篇关于为什么我们在 C++ 中实际上需要 Private 或 Protected 继承?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!

本站部分内容来源互联网,如果有图片或者内容侵犯了您的权益,请联系我们,我们会在确认后第一时间进行删除!

相关文档推荐

Prevent class inheritance in C++(防止 C++ 中的类继承)
Why should I declare a virtual destructor for an abstract class in C++?(为什么要在 C++ 中为抽象类声明虚拟析构函数?)
Why is Default constructor called in virtual inheritance?(为什么在虚拟继承中调用默认构造函数?)
C++ cast to derived class(C++ 转换为派生类)
C++ virtual function return type(C++虚函数返回类型)
Is there any real risk to deriving from the C++ STL containers?(从 C++ STL 容器派生是否有任何真正的风险?)