Re:Why bad scientific code beats code following “best practi...
by jimmaswell on Sunday August 28, 2016 @05:41PM
(#12378677)
The getter/setter problem is solved very nicely by C#. You can change a field to a property at any time without changing the rest of the code, and a lot of the use cases for get/set can be handled compactly like public int X{get; private set;} instead of having to have 2 variables.
[ Parent
| on HN ]
There are no comments on this comment yet.