Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses

Re: Re: Idomatic Handling of Subroutine Error

by btrott (Parson)
on Sep 18, 2001 at 22:50 UTC ( #113171=note: print w/replies, xml ) Need Help??

in reply to Re: Idomatic Handling of Subroutine Error
in thread Idomatic Handling of Subroutine Error

That's not right. eval BLOCK has no overhead (or rather negligible overhead).

eval EXPR (string eval) *does* have overhead, because the string needs to be compiled at runtime, but that's the issue here.

In general, actually, I would tend to agree with you, but for a different reason: there is no sense in wrapping *every* function call in its own eval. Instead wrap an entire self-contained block in an eval, like this:

eval { ... ... ... }; if ($@) { ## Got error }
You will jump out of the block as soon as your code hits an exception, and you might as well keep your exception-handling in one place, rather than scattered all over the place.

To the OP: check out Exception::Class and Error, among others.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://113171]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (10)
As of 2016-10-24 20:20 GMT
Find Nodes?
    Voting Booth?
    How many different varieties (color, size, etc) of socks do you have in your sock drawer?

    Results (309 votes). Check out past polls.