Getter and setter policy
From CSSEMediaWiki
(Difference between revisions)
JaninaVoigt (Talk | contribs) |
|||
| Line 2: | Line 2: | ||
Objects should store all their data in private or protected variables. Getter and setter methods should be produced for any variable you may consider you have a legitimate reason to declare public. Classes should ideally call their own getter and setters when accessing their internal data. This prevents the object getting into a invalid state. | Objects should store all their data in private or protected variables. Getter and setter methods should be produced for any variable you may consider you have a legitimate reason to declare public. Classes should ideally call their own getter and setters when accessing their internal data. This prevents the object getting into a invalid state. | ||
| + | |||
| + | Generally, if you have too many getters and setters, you should have a closer look at your design to make sure you [[Keep related data and behavior in one place]]. | ||
Revision as of 09:17, 30 July 2009
Needing to have getters and setters is bad as they increase coupling. However if need to implement them apply the following guides.
Objects should store all their data in private or protected variables. Getter and setter methods should be produced for any variable you may consider you have a legitimate reason to declare public. Classes should ideally call their own getter and setters when accessing their internal data. This prevents the object getting into a invalid state.
Generally, if you have too many getters and setters, you should have a closer look at your design to make sure you Keep related data and behavior in one place.
