Timeline for Are null references really a bad thing?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 12, 2020 at 15:57 | comment | added | OCDev | So null reference exceptions are a good thing because they let you know there is a problem with the data earlier in the process rather than later after the data problem leads to other problems that make tracking it down very confusing. I think our culture just likes to avoid immediate pain by putting it off and experiencing greater pain. | |
| May 23, 2016 at 11:07 | comment | added | sara | You assume that null is the only (or even a preferable) way of modeling the absence of a value. | |
| Apr 13, 2015 at 19:19 | comment | added | Chris McCall | This is a good answer. The null construct in programming is not the problem, it's all the instances of null values that are. If you make a default object, eventually all your nulls are going to be replaced with those defaults and your UI, DB and everywhere in between will be filled with those instead, which are probably no more useful. But you'll get to sleep at night because at least your program is not crashing I guess. | |
| S Apr 10, 2015 at 23:36 | history | answered | Loren Pechtel | CC BY-SA 3.0 | |
| S Apr 10, 2015 at 23:36 | history | made wiki | Post Made Community Wiki by Loren Pechtel |