On Jun 18, 2004, at 6:13 AM, Karsten Konrad wrote:
Would you also want the filter itself available?
the filter is not so important for me, although I think that all the Filter/Query
classes should make their contents available for postprocessing - setters are
different, but why omit a getter in this context?
I'll turn the question around.... why expose internal state when there isn't a use for it? Returning mutable objects is risky business. What if the developer modifies the returned object? Is that ok?
For the filter, I'll leave that off until a need arises to add a getter.
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
