Your rule would forbid:
if (...) { return A } elsif (...) { return B } elsif (...) { return C } else { die "unmatched case" }
This is why I say it is ridiculous, because I see that construct as a perfectly legitimate way to handle returning different values in different cases. The final die (or a final return undef) is indented along with all of the other cases. Omitting the else would place it one level out. Note that an if-elsif chain like this obviously can have no code following it, but the else here simply highlights that one of these will be executed. Also note that I tend to omit the semicolon after return/last/next/die/etc. in Perl because there should not be another statement after any of those and omitting the semicolon promotes such dead code to a syntax error.
In reply to Re^8: What's the right way to write a method which returns one line at a time from a file?
by jcb
in thread What's the right way to write a method which returns one line at a time from a file?
by Cody Fendant
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |