I think that will also mess up anything which is doing an eval and then checking $@ afterwards.
Does it?
use Carp qw(confess cluck);
BEGIN {
*CORE::GLOBAL::warn = \&cluck;
*CORE::GLOBAL::die = \&confess;
}
sub foo { bar() }
sub bar { print "in bar\n"; die "badness!" }
eval { foo };
print "ack - $@" if $@;
__output__
in bar
ack - badness! at - line 8
main::bar() called at - line 7
main::foo() called at - line 10
eval {...} called at - line 10
Same goes for throwing objects
use Carp qw(confess cluck);
BEGIN {
*CORE::GLOBAL::warn = \&cluck;
*CORE::GLOBAL::die = \&confess;
}
sub foo { bar() }
sub bar { print "in bar\n";die( bless{akey=>"a string"} ) }
use DDS;
eval { foo };
print "ack: ", Dump($@) if ref $@;
__output__
in bar
ack: $main1 = bless( { akey => 'a string' }, 'main' );
So Aristotle's solution should fit the bill.
-
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.
|