Hacker News new | ask | show | jobs
by patrickmay 3727 days ago
> The getX() and setX() is an anti-pattern of good OOP.

This needs to be tattooed in reverse on many developers foreheads so it's the first thing they read when brushing their teeth in the morning.
1 comments
UK-AL 3727 days ago
Problem is developers take that as an excuse to make state public, which is even worse.
link
kasey_junk 3727 days ago
It doesn't matter whether you make the state public via a getter or via variables (modulo some compiler specific reasons to use accessors).

If your design is allowing some external actor to work with multiple parts of the state of a behavior driven object (ie not a record) accessors are not going to help you, you've still exposed the state.

link
UK-AL 3727 days ago
Completely agree.

But at least with getters/setters you can intercept calls before they modify state.

But you should design so you don't need this in the first place.

link