When virtual inheritance IS a good design?

by

If you have an interface hierarchy and a corresponding implementation hierarchy, making the interface base classes virtual bases is necessary.

E.g.

struct IBasicInterface
{
    virtual ~IBasicInterface() {}
    virtual void f() = 0;
};

struct IExtendedInterface : virtual IBasicInterface
{
    virtual ~IExtendedInterface() {}
    virtual void g() = 0;
};

// One possible implementation strategy
struct CBasicImpl : virtual IBasicInterface
{
    virtual ~CBasicImpl() {}
    virtual void f();
};

struct CExtendedImpl : virtual IExtendedInterface, CBasicImpl
{
    virtual ~CExtendedImpl() {}
    virtual void g();
};

Usually this only makes sense if you have a number of interfaces that extend the basic interface and more than one implementation strategy required in different situations. This way you have a clear interface hierarchy and your implementation hierarchies can use inheritance to avoid the duplication of common implementations. If you’re using Visual Studio you get a lot of warning C4250, though.

To prevent accidental slicing it is usually best if the CBasicImpl and CExtendedImpl classes aren’t instantiable but instead have a further level of inheritance providing no extra functionality save a constructor.

More Related Contents:

  1. How does virtual inheritance solve the “diamond” (multiple inheritance) ambiguity?
  2. Object layout in case of virtual functions and multiple inheritance
  3. Virtual tables and memory layout in multiple virtual inheritance
  4. In C++, what is a virtual base class?
  5. Why do multiple-inherited functions with same name but different signatures not get treated as overloaded functions?
  6. c++ virtual inheritance
  7. Why should I avoid multiple inheritance in C++?
  8. Why is Default constructor called in virtual inheritance?
  9. Disambiguate class-member in multiple inheritance
  10. Why exactly do I need an explicit upcast when implementing QueryInterface() in an object with multiple interfaces()
  11. Inherit interfaces which share a method name
  12. ‘Inaccessible direct base’ caused by multiple inheritance
  13. C++ inherit from multiple base classes with the same virtual function name
  14. Diamond inheritance (C++)
  15. C++ pointer multi-inheritance fun
  16. Multiple Inheritance from two derived classes
  17. Why can’t static_cast be used to down-cast when virtual inheritance is involved?
  18. C++ multiple inheritance function call ambiguity
  19. How can I avoid the Diamond of Death when using multiple inheritance?
  20. Order of constructor call in virtual inheritance
  21. Why must virtual base classes be constructed by the most derived class?
  22. Understanding virtual base classes and constructor calls
  23. Why can’t I use inheritance to implement an interface in C++? [duplicate]
  24. Invalid covariant type with CRTP clonable class
  25. What is the VTT for a class?
  26. using declaration in variadic template
  27. Difference between ‘struct’ and ‘typedef struct’ in C++?
  28. A most vexing parse error: constructor with no arguments
  29. Convert CString to const char*
  30. int to unsigned int conversion

Leave a Comment