Timeline for Overused or abused programming techniques
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 1, 2011 at 13:01 | comment | added | Wayne Molina | Now that I think of it, that's a fair point. | |
| Sep 1, 2011 at 12:57 | comment | added | configurator | @Wayne: How is changing ; to { get { ... } set { ... } } any more work than changing { get; set; } to { get { ... } set { ... } }? | |
| Aug 31, 2011 at 20:24 | comment | added | Wayne Molina | Agreed; if you know 100% you will never need to do anything with getting/setting a "property" then there's no reason whatsoever to have a property. However, if there's a chance you will need to do something (logging that a value was changed, for instance) then you should use a property. Personally I don't see a big enough difference to not use the property, just in case you do need to modify it later (I know, I know YAGNI but I feel deviating in this case doesn't cost anything) | |
| S Aug 31, 2011 at 16:30 | history | answered | configurator | CC BY-SA 3.0 | |
| S Aug 31, 2011 at 16:30 | history | made wiki | Post Made Community Wiki by configurator |