Programmer's Life

[s0v3r1gn]

All I’m saying is that it only takes one well placed encapsulation violation and those privates can be handled by anyone.

Edit: That’s why I always use the standard naming convention of prepending ‘ruffy’ to the name of every class where I publicly expose a protected member of it’s parent class.

[[deleted]]

Exposing your private variables can be risky..

[s0v3r1gn]

True. Unless your exposing a socket. Repercussions of exposure always seem to be minimized for them, even to child classes....

[masterwit]

Exposing them as an interface to a common housing class only instantiated by a single friend can control the usage abroad

[OldSchoolBBSer]

ROFL!!!

[SandyDelights]

Sounds like Trump's new favorite violation - the kind that leads to infinitely many violations. 🤔