Thread: to inherit or not to inherit ...

Originally Posted by CornedBee

Scanning my largest and most complex C++ project, the only case where I've used private inheritance is to derive from boost::noncopyable, and that's a very special base class.

Interesting. I take it that boost::noncopyable is like a policy class to forbid assignment and copy construction? So I guess there could be at least two reasons to derive privately, huh?

I like the idea of wrapping that into a policy class instead of declaring those two functions private and not defining them. If anything, the clarity alone seems to be worth it.

Use composition (first example), and use a std::vector of smart pointers, not an array, of TabItems.