As portrayed in Multiple Inheritance, a class can be gotten from more than one base class. In a numerous legacy model (where classes are gotten from more than one base class), the base classes are indicated utilizing the base-list linguistic use component (see the Grammar segment in Overview). For instance, the class announcement for Collection of Book, got from Collection and Book, can be indicated:

“// deriv_MultipleBaseClasses.cpp
// compile with: /LD
class Collection {
};
class Book {};
class CollectionOfBook : public Book, public Collection {
// New members
};”

The request in which base classes are determined is not huge with the exception of in certain situations where constructors and destructors are summoned. In these cases, the request in which base classes are determined influences the accompanying:

The request in which introduction by constructor happens. On the off chance that your code depends on the Book segment of Collection of Book to be introduced before the Collection part, the request of determination is noteworthy. Instatement happens in the request the classes are determined in the base-list.

The request in which destructors are summoned to tidy up. Once more, if a specific "part" of the class must be available when the other part is being annihilated, the request is huge. Destructors are brought in the converse request of the classes determined in the base-list.

While indicating the base-show, you can't determine the same class name more than once. Be that as it may, it is workable for a class to be a circuitous base to an inferred class more than once.