Skip to main content

Explain use of Private Inheritance

The use of public inheritance implies an is-a relationship between a base class and its descendant. Unlike public inheritance, private inheritance is used when you want to inherit the implementation of the base class without the is-a commitment. Thus, if A is a non-public base of B, B has access to all the non-private members of A, but it's not an A. In this regard, private inheritance is almost identical to containment. When should you use private inheritance? Suppose you want to create a collection of objects of a certain type while reusing the functionality of another container class, say, Stack. You don't want your derived class D to behave as a Stack, you simply need the implementation of the Stack class. In this case, you privately derive D from Stack:
class Stack
{
public:
void push(Element &);
void pop();
}
class B: private Stack
{
public:
int insert(const Element & e)
{
push(e); // reuse Stack::push
}
};
Note that the use of private inheritance allows you to change the implementation of B::insert transparently. You may decide at a later stage to use a different container instead of Stack without affecting B's users, who have no access to the actual implementation anyway.
Labels:

Comments

Post a Comment

Popular posts from this blog

Explain Polymorphism and Flavors of Polymorphism...

Polymorphism is the ability of different objects to react in an individual manner to the same message. This notion was imported from natural languages. For example, the verb "to close" means different things when applied to different objects. Closing a door, closing a bank account, or closing a program's window are all different actions; their exact meaning is determined by the object on which the action is performed. Most object-oriented languages implement polymorphism only in the form of virtual functions. But C++ has two more mechanisms of static (meaning: compile-time) polymorphism: Operator overloading. Applying the += operator to integers or string objects, for example, is interpreted by each of these objects in an individual manner. Obviously, the underlying implementation of += differs in every type. Yet, intuitively, we can predict what results are. Templates. A vector of integers, for example, reacts differently from a vector of string objects when it receives ...
17 comments
Read more

Function name mangling for C++ and Java

G++ internals - Mangling Both C++ and Jave provide overloaded function and methods, which are methods with the same types but different parameter lists. Selecting the correct version is done at compile time. Though the overloaded functions have the same name in the source code, they need to be translated into different assembler-level names, since typical assemblers and linkers cannot handle overloading. This process of encoding the parameter types with the method name into a unique name is called name mangling . The inverse process is called demangling . It is convenient that C++ and Java use compatible mangling schemes, since the makes life easier for tools such as gdb, and it eases integration between C++ and Java. Note there is also a standard "Jave Native Interface" (JNI) which implements a different calling convention, and uses a different mangling scheme. The JNI is a rather abstract ABI so Java can call methods written in C or C++; we are concerned he...
5 comments
Read more