comment on

Error handling in Perl follows the maxim that there is more than one way to do it.

For starters, there is the simple "do or die" syntax known from such "phrases" as

open(....) or die "Could not open ... $!\n";
[download]

(there is also a variant a variant called warn which sends the same output to STDERR, but doesn't terminate the program.

Some modules deliver errors in parameters (i.e. returning 0 from a particular subroutine), others die.

Some (like DBI with it's RaiseError/PrintError can do either or both.

There are several modules that install their own handlers for die/warn, the most used is probably CGI::Carp which shows the error messages on the browser screen instead of in the web server's error log.

If you want to handle errors differently, in a java-ish, object oriented way, you might want to check out Error. It implements the try/catch method of error handling.

In reply to Re: How to handle Errors? by matija
in thread How to handle Errors? by Scarborough

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


laziness, impatience, and hubris
	PerlMonks