Re^3: How many different ways can Perl code fail?

Why is using $@ a bit unreliable?

Update: Just found that the answer to this is covered by the documentation of Devel::EvalError. A quick read seems to suggest that the issue can only arise if there's a DESTROY method which uses eval (however indirectly) and doesn't localise $@.

You'll have to decide whether that would be a problem for you...

--
use JAPH;
print JAPH::asString();

Comment on Re^3: How many different ways can Perl code fail?

Replies are listed 'Best First'.
Re^4: How many different ways can Perl code fail? by ikegami (Patriarch) on Jan 14, 2009 at 18:00 UTC
You'll have to decide whether that would be a problem for you... Not really. It's not like it's harder to handle the problem. I'd say it's even cleaner. `eval { ... }; if ($@) { ... }` [download] vs `eval { ...; 1 } or ...;` [download] and `my $x = eval { ... }; if ($@) { ... }` [download] vs `my ($x) = eval { ... } or ...;` [download]	[reply] [d/l] [select]