in reply to Re: Style Point: Catching eval { } errors
in thread Style Point: Catching eval { } errors

If you want to be creative, and can actually stand the function prototypes, you can do this:
sub try (&@) { my($code, $error_handler) = @_; eval { $code->(); }; $error_handler->() if $@; } sub catch (&) { return @_; }
The & allows you to pass code blocks directly without the sub keyword. You can then write:
my $msg; try { open (FILE, "strangefilename") || die "$!"; $msg = <FILE>; } catch { print "File could not be opened because of: $@\n"; $msg = "BAAAAH"; }
This code is from the perlsub perldoc page.

Replies are listed 'Best First'.
Re^3: Style Point: Catching eval { } errors
by Aristotle (Chancellor) on Nov 28, 2003 at 15:30 UTC
    This is what Exception lets you do, and unfortunately has numerous problems. The simplest gotcha of all - did you notice your last snippet is missing a semicolon?

    Makeshifts last the longest.