Probably neither, but refactoring code depends a great deal on the context and you haven't given us enough to play with. Personally I make frequent use of early exit and often use exceptions to handle error recovery. Early exits tend to reduce nesting blocks and exceptions take care of "jumping out of code" on errors. Maybe something like:

for my $gas_cost (@gasCosts) { if ($gas_cost < 1) { print "Bad gas - $gas_cost\n"; next; } ... }

or:

eval { die "Bad gas - $gas_cost\n" if $gas_cost < 1; ... return 1; } or do { my $err = $@; print "Error handling gas: $err" };
Premature optimization is the root of all job security

In reply to Re: How to no goto or gosub by GrandFather
in thread How to no goto or gosub by oldcity

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.