Hello shmem,
Why don't we have @@ as an error stack, ...?
FWIW, Exception::Class::TryCatch:
...provides for a method to push errors onto a hidden error stack immediately after an eval so that cleanup code or other error handling may also call eval without the original error in $@ being lost.
For example:
#! perl
use strict;
use warnings;
use Exception::Class::TryCatch;
try eval
{
my $bar = baz();
die 'baz failed!' if $@;
};
if (my ($second, $first) = (catch, catch))
{
print "(1) $first(2) $second";
}
sub baz
{
try eval "1 = 2";
}
Output:
18:09 >perl 1447_SoPW.pl
(1) Can't modify constant item in scalar assignment at (eval 4) line 1
+, at EOF
(2) baz failed! at 1447_SoPW.pl line 9.
18:09 >
Hope that’s of interest,
-
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.
|