These are two ways to describe the relationship between classes. Discuses the situations in which, concept of public inheritance and nested class is more appropriate to use. Justify with solid reasons.

please provide the answer

your comment makes Alex’s article more understandable, specially for Beginners, most of the times they become confused at this point, but if they follow your table they never confused LIKE ME :)

Thanks & Regards
Nikhil Singhal

What you say is:
Public -> Public
Protected -> Protected
Private -> Private

This is how I would change your table, putting a “-” to the appropriate cell:
public -> public
protected -> protected
private -> -

Same applies to protected inheritance:
public -> protected
protected -> protected
private -> -

And for private inheritance:
public -> private
protected -> private
private -> -

So in my interpretation, there is an even easier way to memorize all 3*3 cases:
First, you’d need to point out, that private is private. No matter how you inherit, a private member will NOT be accessible in the derived class.

So here it is how I’d let people memorize it:
0. Inheritance specifier is uninterpretable for private members.

1. PUBLIC inheritance: Everything remains the SAME in the derived class:
public -> public
protected -> protected

2. PROTECTED inheritance: Everything becomes PROTECTED in the derived class:
public -> protected
protected -> protected

3. PRIVATE inheritance: Everything becomes PRIVATE in the derived class:
public -> private
protected -> private

This is how I was taught it, and I think that it is much simpler this way.

THANKS.