Bug #74639 for Term-ANSIColor: Constants eat $@

Thu Feb 02 15:01:47 2012 simonw [...] cpan.org - Ticket created

Subject:

Constants eat $@

we were doing something like my $val = eval { some_call }; if ($@) { print BOLD, RED, "Error: ", RESET, $@,"\n"; } else { print "Value = $val\n"; } and couldn't understand why errors wouldn't come through. We eventually realised that they would come through but only on the second time which eventually led us to realising that you had an eval in AUTOLOAD which was eating our $@ Could you either document that or preserve the $@ in AUTOLOAD?

Sun Mar 18 17:46:51 2012 rra [...] stanford.edu - Correspondence added

Subject:	Re: [rt.cpan.org #74639] Constants eat $@
Date:	Sun, 18 Mar 2012 14:46:41 -0700
To:	bug-Term-ANSIColor [...] rt.cpan.org
From:	Russ Allbery <rra [...] stanford.edu>

"Simon Wistow via RT" <bug-Term-ANSIColor@rt.cpan.org> writes: Show quoted text

> we were doing something like

Show quoted text

> my $val = eval { some_call }; > if ($@) { > print BOLD, RED, "Error: ", RESET, $@,"\n"; > } else { > print "Value = $val\n"; > }

Show quoted text

> and couldn't understand why errors wouldn't come through.

Show quoted text

> We eventually realised that they would come through but only on the > second time which eventually led us to realising that you had an eval in > AUTOLOAD which was eating our $@

Oh, indeed, good catch. This is now fixed in the just-released 3.02, which should be showing up on CPAN shortly. Thank you! -- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>

Sun Mar 18 17:46:52 2012 The RT System itself - Status changed from 'new' to 'open'

Sun Mar 18 17:52:29 2012 RRA [...] cpan.org - Status changed from 'open' to 'resolved'

Mon Dec 31 13:30:24 2012 RRA [...] cpan.org - Fixed in 3.02 added