in reply to Style Point: Catching eval { } errors

You can even get creative: 
if(eval {
    # Do stuff
}, $@) {
    # Handle any errors
}

[download]
:-)

Makeshifts last the longest.

Replies are listed 'Best First'.
Re: Re: Style Point: Catching eval { } errors
by dref (Novice) on Nov 28, 2003 at 12:29 UTC
    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 @_;
}

    [download]
    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";
}

    [download]
    This code is from the perlsub perldoc page.
[reply]
[d/l]
[select]
      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.

[reply]

In Section Meditations