Timeline for How 'child proof' should I write code as a solo programmer?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 24 at 10:07 | comment | added | gnasher729 | @misterbiscuit Null checks are often implicit. If I write p->x = 0 then the hardware automatically performs a null pointer check which either falls into the debugger when I run on a development machine or crashes instantly. So you have more null pointer checks than you think. On the other hand if your manual null pointer check achieves not more than you could as well remove it. | |
| Sep 2, 2014 at 16:21 | comment | added | misterbiscuit | If within a given situation something should never be null then you should not check for null. Nulls could arise from another person trying to use code in a way it wasn't designed for. They deserve it to explode. I write a lot of Java. In some ways it can be even harder to properly structure and manage errors. When i see devs with catch blocks all over the place i want to puke because they dont understand that error should not be caught for the sake of catching errors but because something useful should be done when it is caught. | |
| Sep 1, 2014 at 21:05 | history | answered | Andy | CC BY-SA 3.0 |