Thanks for creating this node. I've often wondered if what I'm doing is the right thing. I tend to flip-flop between both methods based on the following criteria:
* If the routine has flow modifiers like goto or next, I use a single return statement.
* If the routine has no flow modifiers and has code duplication that aids readability, I use multiple return statements to keep each duplicated section independent (they can now be jettisoned on-demand).
* If the routine has flow modifiers and code duplication, I use multiple return statements with a debug print statement before every return (during development). I also suddenly turn religious and start praying.
Writing mostly baby Perl (see "Baby" Perl versus "Bad" Perl), though, means I don't really adhere to "coding standards".
~RecursionBane
In reply to Re: Control Flow - Multiple returns or nested conditionals
by RecursionBane
in thread Control Flow - Multiple returns or nested conditionals
by JediWizard
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |