Arnd,



Thank you for your response. I understand what you're saying: that private is only class private because instances of the same class can call the private functions or modify the private instance variables in other instances of the same class, but I'm having problems understanding how you would for example code a class to make a call from one instance of that class to a private function in another instance of the same class.



When coding the class the instances don't exist. How can I code the constructor event of a class for example to call a private function in instance B of the class from instance A of that very same class? It's this "chicken and egg" problem that I can't get my head around.



Regards,

Michael.

I think the whole question is more an academic point of view.

The question is how instance A can get a reference to Instance B - you mention the constructor.

You can also have a public function in your class that accepts an instance of the class as an argument.

In such a public function you can modify the private instance variables or call any private function in the instance of the argument. I do not want to discuss "readonly" here :-)

All in all it seems that these "solutions" lead to ...let's say ... bad code. Why would you write such a class? Because you can?!

But the statement about "class private" makes sense in a kind of academic way. For sure the statement is more irritating than it helps.

I found the other Q&A. Eventually the statement of your documentation was inspired by this discussion:

https://community.appeon.com/index.php/qna/q-a/when-private-access-is-not-entirely-private-bug-or-feature



regards



Arnd