Timeline for Assertion failure that a null pointer exception is caught
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 8, 2019 at 21:03 | vote | accept | Arthlete | ||
| Feb 9, 2016 at 5:22 | comment | added | cropredy | i kind of like having the general exception catcher include the stacktrace as I can at least hope the end user will send me a screen shot and I can diagnose without having to track the user down to reproduce the issue - especially with a global user base. I'm also with @crmprogdev here where data migrations and legacy unmigrated data sometimes comes back to haunt you - yes better procedures and rigorous SDLC and ISO 9001 type stuff could avoid this, but the all singing, all dancing sysad/dev sometimes doesn't have the bandwidth for this. But - I agree with all that is said above | |
| Feb 8, 2016 at 20:10 | history | edited | Keith C | CC BY-SA 3.0 |
added 1 character in body
|
| Feb 8, 2016 at 19:51 | comment | added | crmprogdev | I think there's a common (mis)perception that exceptions always represent coding errors. It's been my observation that they represent data input errors or a failure to validate either the type of incoming data or catch data that is "out of bounds". This data later becomes problematic when being processed by our code. When we rely on the UI to validate, then data is later imported via bulk, that's when we esp encounter these problems. | |
| Feb 8, 2016 at 18:55 | comment | added | Adrian Larson♦ |
I'm a little leery of the advice "It is often be better to not add logic that tries to handle programming errors." I think without a little more context it could be mistaken. I also think it's somewhat bad practice to catch a generic Exception without knowing specifically which type you are guarding against (even if it's just copy-pasta). Otherwise worthy of a +1.
|
|
| Feb 8, 2016 at 18:43 | history | edited | Keith C | CC BY-SA 3.0 |
added 265 characters in body
|
| Feb 8, 2016 at 18:37 | history | answered | Keith C | CC BY-SA 3.0 |