For example normally DBI errors are fatal to the entire program. However, if I wrap my DBI calls in an eval BLOCK structure I can then catch a fatal DBI error and take steps to deal with that in my program such as logging it, restarting the database connection, etc. The important thing is that the fatal error doesn't take my script with it.

Personally I think using the same name is confusing. I would have preferred something like 'catch BLOCK' instead (or perhaps 'exception BLOCK').

Here's some 'eval BLOCK' code I use:

sub cmd_wrapper {
    my( $cmd ) = @_;
    my( $rc , $out );

    eval {
        local $SIG{ALRM} = sub { die "alarm\n" };
        alarm 15;
        $out = (`$cmd`)[0]; # Get first line of output
        $rc = $?;
        alarm 0;
        };

    if( $@ ) {
        die "Eval failed for $cmd but not because of alarm" if $@ ne "
+alarm\n"; # Propogate unexpected errors
        die "Eval failed for $cmd because alarm timed out";
        }

    die "Return code undefined for $cmd" unless defined $rc;
    return $rc, $out if wantarray;
    return $rc;
    }
[download]

See also Corion's post: Re: nested variable resolution.