Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Why protected and private inheritance are defined and proposed? I understand some cases private inheritance could be used but it is not recommended. How about protected inheritance?
Can anyone offer me an situation in which protected inheritance is a choice?
I rarely see this.
Thanks so much!
Private inheritance is usually used for mixins—where people inherit to get functionality from the base class, rather than because of “is-a” inheritance.
Protected inheritance can also be used for mixins, where the mixed-in functionality is to be available to downstream classes too.