You could use dualvar and a hash...
use Scalar::Util qw(dualvar);
my %Error=(220=>"Cannot connect to service");
sub mysub {
if (@_) {
return dualvar(0,1);
} else {
return dualvar(220,0);
}
}
my $x;
$x=mysub() or die $Error{$x};
Of course this still leaves the problem of where to put the error, in the return or in a global. I think your options range from using something like $Pack::Error (which is IMO infinitely preferable to using the magic global $_), using $@ or using something like ${^MYERROR}. For instance I think the following is a reasonable approach:
use Scalar::Util qw(dualvar);
my %Error=(220=>"Cannot connect to service");
sub mysub {
if (@_) {
$@=dualvar(0,1);
} else {
$@=dualvar(220,0);
}
return $@
}
mysub() or die sprintf "%d %s",$@,$Error{0+$@};
Assuming that you dont have any eval checking logic that this will interfere with (and im not seeing immediately how that could happen anyway) then it should be ok.
-
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.
|