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" };
In reply to Re: How to no goto or gosub
by GrandFather
in thread How to no goto or gosub
by oldcity
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |