comment on

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
[download]

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' );
[download]

So Aristotle's solution should fit the bill.

HTH

_________ broquaint

In reply to Re^3: Automatic stack traces for warns and dies by broquaint
in thread Automatic stack traces for warns and dies by fergal

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.


Problems? Is your data what you think it is?
	PerlMonks