in reply to Re: Best Practices for Exception Handling
in thread Best Practices for Exception Handling
Some reasons I like exceptions:
Robustness. I can forget to check for an returned error value. I cannot forget to check for an exception.
Brevity. I prefer:
$o->foo or return(ERROR_FOO);
$o->bar or return(ERROR_BAR);
$o->fribble or return(ERROR_FRIBBLE);
$o->ni or return(ERROR_NI);
Clarity. With exception based code the "normal" flow of control is more explicit because it is not obscured by error handling code. I think that the first of the two code examples above shows the intent of the code more directly than the second does.
Separation of concerns. The error condition and the error handler are different ideas.
- You may want an error to be handled in different ways depending on the context.
- You may also not know how the error should be handled at the point it occurs.
- You may not know how the error should be handled at the time you write the code.
With the return-error-code style you end up having to either:
- propogate error conditions to where the decision on how they should be handled can be made.
- propogating error handlers down to where the errors may occur
Both options rapidly become messy if there are many levels of code between the error condition and the error handler.
No confusion between return values and error conditions.
There are probably some more ;-)