When writing a Perl module, is it a good practice to use croak/die inside the module?
After all, if the caller doesn’t use an eval block, the module might crash the program calling it.
What is the best practice in these cases?
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I generally prefer exceptions if you’re indicating an error of some kind. Otherwise you have to spend much more time sprinkling error handling code at different levels of your codebase rather than centralising the error handling in appropriate layers of the system – amongst other reasons.
You may find this old thread on perlmonks a useful read. I’ll reproduce my comment there below – since I mostly agree with what I wrote back then 🙂
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:
to
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 😉