🚀 go-pugleaf

In article c95@steel.interlog.com, herbs@interlog.com (Herb Sutter) writes:
>
>"What is protected inheritance?"

>Through experience, I now know the answer.  However, by far the most common 
>(and wrong) idea I keep hearing is that it was 'put in for completeness' since 
>we already have public and private inheritance, but that no one really knows 
>what it's good for.  

The only reason for protected inheritance I ever saw or heard was for
symmetry and because there seemed to be no reason to disallow it.

>...  In 
>contrast, I've recently come upon two detailed examples in my own work where 
>it is both necessary and elegant. ...

>If the above literature really reflects the state of the industry, I should 
>write a few articles. 

Please do. I always find it a bit embarassing when teaching C++ to
describe protected inheritance as a solution in search of a problem.

---
Steve Clamage, stephen.clamage@eng.sun.com




---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]