On 10/19/07, Sean O'Halpin <sean.ohalpin / gmail.com> wrote:
> Because it's not needed and it's considered bad style to introduce
> unnecessary noise in Ruby. Every method call returns a value. In the absence
> of a return statement, it is the value of the last expression in the
> definition. So, whether you want it or not, it happens. Better to get used
> to that, take advantage of it and save yourself a few keystrokes than to
> think that you typing return at the end of a method definition makes any
> difference at all.
>
> The only time to use return is when you return from the middle of a method,

You're doing great up until

> but even that is considered bad programming practice (functions should have
> only one exit).

which is just ridiculous.

Pat