Aren't the vast majority of use cases hypothetical? Our job when constructing software isn't to look at what is being done, but to look at what could be done. Otherwise we're not making any improvement.
In terms of API, I would tend to err on the side of more public access rather than less. There's no harm in public methods while private ones can deter and delay development. On Apr 18, 2009, at 9:16 PM, Sean Coates wrote: > Obviously we disagree. The use case you mention is hypothetical. I > could make a hypothetical use case for any non-public property. > Reality is that the real solution to the only existing known problem > was to change the constructor, and protected or private (not > advocating private in this case) reduce that API maintenance burden, > so it has some value. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
