Neil Santos wrote:
private hiddens from outside world, not from descendants of an object.
Isn't that what `protected' is for?
Yes, indeed.
However, `private' means unit/modules wide visibility. -- One could discuss how useful it is, but since we follow (mostly) BP's object model, that's just the way it is. (Perhaps it was meant for purposes similar to C++'s `friend'.)
Therefore, there can be conflicts even with private fields.
Frank