Possible Duplicate:
Do write-only properties have practical applications?
A getter without a setter makes total sense, of course. Read-only property. Got it, no problem.
But I’m maintaining some code right now where there are setters but no getters and I’m kind of puzzled by that.
Is there any reason I should be hesitant about adding getters? It’s hard for me to imagine a setting where it’s OK to change a value to whatever the caller wants (there’s no sanity checks in the setters), but wherein it’s not OK to tell the caller what the current value is.
The code happens to be PHP, if that matters for some reason.
As pointed out in Do write-only properties have practical applications?, setting a seed for a random number generator is a pretty straightforward case where it totally makes sense to have a setter without a getter.