Am 19.01.2013 16:26, schrieb Jacob Carlborg:
On 2013-01-19 03:50, Andrey wrote:
I haven't seen such situations yet. According to OOP concept they must
be very rare, so I tend to consider them more of architecture and logic
mistake (and C++ is one big architecture and logic frankenstein).
In theory and according to the OOP concept they might not be needed but
when it comes to actually implement a OO concept it can turn out to be
handy to have. That is, accessing a private member in the same module.
I do use it a lot when doing unit tests that check for side effects in
the private data (JVM/.NET) of objects.
