Possible @property compromise

TommiT tommitissari at hotmail.com
Wed Jan 30 13:40:23 PST 2013


On Wednesday, 30 January 2013 at 21:26:34 UTC, 1100110 wrote:
> Me either.
>
> I mean yes, for anything that is part of a public api you 
> should probably double check everything.  But insisting on 
> getters and setters regardless of the requirements of what you 
> are getting and setting?
>
> Sounds like an excuse to not think, to me.

Putting in public variables sounds like not thinking, to me. 
Interface should expose the minimum amount of access possible, 
whereas public variables expose the maximum amount of access.


More information about the Digitalmars-d mailing list