Using goto to get out of a subroutine is not something I've seen before - except in BASIC, where doing so leaves a mess on the call stack. And in assembly, where it also leaves a mess unless the coder explicitly cleans up the stack.

While it is true that using goto can avoid deeply nested conditionals, it's generally better to set an error variable and use last:

my $error;
{
    ...;
    $error = 'message', last if ( $foo == $bar );
    ...;
}
if (defined $error) {
    ...; # clean up mess and/or warn the user
}
[download]

And your code is using a variable behind the scene, so this just brings the variable into the foreground.

But, if you really don't like that, you could try:

{
    do {
        ...;
        $foo == $bar and warn 'foo bar problem';
    } or do {
        ...;
    } or do {
        last;
    }
    ...; # clean up mess
}
[download]

(I think warn will return a non-0 value. If not, does print?)