All the more reason to avoid implicit return statements.

sub Sa {
    foo();  # implicit return: foo() called in Sa() invocation context
+.
    }

sub Sb {
    return foo();  # explicit return: foo() called in Sb() invocation 
+context.
    }

sub Sc {
    foo();  # foo() called in void context. no question.
    return;
    }
[download]

And also IMH (but very emphatic!) O, one should certainly avoid weird "implicit return of 1" statements which are no more than maintainence pitfalls.

IMHO, the Sa() form should always be avoided.

Why? I can't think of a single problem that solves.

I think TheDamian's PBP has a convincing discussion of the evils of the implicit return. The chief benefits (IMHO) of an explicit return are improved clarity and maintainability of code.

---

Give a man a fish:  <%-(-(-(-<

I agree, and so does Perl::Critic::Policy::Subroutines::RequireFinalReturn.

:) I missed it too but Reply is reply - read, eval, print, loop, yay!

1; is shorter than return;