Other posters have mentioned exceptions; that's a good way to
go.
Another option is more similar to the sample code you posted.
If you are willing to call your subroutines as object or class
methods, you can have your methods return undef on error,
and set either an instance variable or a class variable, which
the calling code can then access using some other method you
set up, like 'errstr'. For example, here is some error-handling code
I use:
use vars qw( $ERROR );
sub new { bless {}, shift }
sub error {
my $msg = $_[1];
$msg .= "\n" unless $msg =~ /\n$/;
if (ref($_[0])) {
$_[0]->{_errstr} = $msg;
} else {
$ERROR = $msg;
}
return;
}
sub errstr { ref($_[0]) ? $_[0]->{_errstr} : $ERROR }
In your methods you can now do:
return $obj->error("Got an error") unless $foo; ## OR
return $class->error("Got an error") unless $foo;
And in the calling code you can do:
$obj->foo or die $obj->errstr; ## OR
My::Class->foo or die My::Class->errstr;
-
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.
|