3 ms·
Your users typically don't want the program to crash, spare a thought for them. Re stack traces, they're fine I guess, but I prefer a well-crafted error messag
by grey-area 5y ago
Your users typically don't want the program to crash, spare a thought for them.
Re stack traces, they're fine I guess, but I prefer a well-crafted error message to 200 lines of irrelevant file locations/functions.
- JoeyJoJoJr 5y agoI want my program to crash obviously during development so that I know of the existence of bugs, which can be ironed out before getting to production.
- grey-area 5y agoThat's the theory. In practice it's impossible to exercise all the inputs your programs may get, and then they crash in production when users do things you don't expect.
- kaba0 5y agoThat’s the point of exceptions. They bubble up! I can manage them at a place where it is appropriate. Something had happened during the processing of this web request? Catch the exception and convert it to an appropriate status code. You should only ever let exceptions fall through ”main” when the problem is really not something you can manage to handle.
- grey-area 5y agoThat's the theory. In practice often people let the exception eater in main handle it, and it either logs somewhere nobody looks or returns this sort of generic error and exits: https://www.google.com/search?q=Microsoft+Word+has+encountered+a+problem+and+needs+to+close https://www.google.com/search?q=Microsoft+Word+has+encounter...