multiple inheritance

[CaseyLamers1]

I want to suggest implementing multiple inheritance.

I find that I regularly want to use building blocks in my applications.  

An example from my project:  I need a serial device class and an analog device class.  I have a power supply class and a flow controller class.  Now if I have a "serial flow controller" or a "analog flow controller" I could have a Flow Controller base class and use serial or analog children.  Or I could say I have a Serial base class and Power Supply and Flow Controller children.  Either way I end up duplicating one set of code, specifically any configuration type settings via data accessors.

I believe multiple inheritance would fix this.

[tst]

This is what NI has to say about it - http://www.ni.com/white-paper/3574/en#toc4

What's your opinion after reading that?

[drjdpowell]

Reminds me of this idea for Traits as a better alternative to things like multiple inheritance.

[Darren]

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.

[_Y_]

The original post is old but still Google-searchable. So, this is solution for

multiple inheritance that works with GOOP4 classes: https://azinterface.net/