Sorry, I can see why my example is confusing. Here's a slightly better one, more true to the production code: 

#!/usr/bin/perl

use strict;
use warnings;
use Scalar::Util qw(looks_like_number);

my @times = (2, 4, 3, 1, 3.5, 2, 5);

select((select(STDOUT), $|=1)[0]);

TIME: for my $time_to_wait (@times) {
    print "Time to wait is: $time_to_wait\n";

    local $@;
    eval {
        # Skip even numbers.
        die '__NOT_FATAL__' if !($time_to_wait % 2);

        verify_number($time_to_wait);

        # Skip numbers less than 3.
        die '__NOT_FATAL__' if ($time_to_wait < 3);

        verify_time($time_to_wait);
        1;
    }
    or do {
        if($@ && $@ =~ /__NOT_FATAL__/) {
            next TIME;
        }

        print "Something went boom! ($@)\n";
    };

    print "Sleeping for $time_to_wait seconds ... ";
    sleep $time_to_wait;
    print "Done.\n";
}

exit 0;

sub verify_number {
    my ($arg) = @_;
    die "We died!" if !defined $arg;
    looks_like_number($arg) or die "We died!";
    return;
}

sub verify_time {
    my ($arg) = @_;
    die "We died!" if !defined $arg;
    # Floats not allowed.
    int($arg) == ($arg / 1) or die "We died!";
    return;
}

[download]

Now imagine several more "verify" type calls within that same eval. Granted, it could be re-written to use a bunch more separate eval calls thus potentially allowing next calls outside/between them but in production those function calls are all very related and would die in similar ways. So I feel it comes down to what's more simple, cleaner? I think I might give the undermentioned Syntax::Keyword::Try package a try (swidt) since it does seem to support exiting via "next" calls.

-s1m0n-

In reply to Re^3: Exiting eval via next: is that so bad? by SimonSaysCake
in thread Exiting eval via next: is that so bad? by jplindstrom

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.