Thanks,
So – if ever implemented & like the C language – is a way to allow another class to access the ‘private/protected’ part of another one: it’s a sort of ‘authorization’.
Considering the stackoverflow’s example, If you write a ‘base’ class and don’t specify what are ‘your’ friends immediately, you need – in future – to change the base every time you would like to access the protected things.
With this logic, make everything private, and add – then- only the sub-classes authorized.
In a ‘public’ project (where different heads have different visions) this approach is very limiting.
Honestly, I don’t like very much the ‘private’ thing at all (or the need to make a method Overridden in the main class!), this feature is just another complication in code design to me!
Thanks anyway!