On Oct 19, 2:10 pm, Greg Donald <g... / cyberfusionconsulting.com>
wrote:
> On Sat, 20 Oct 2007, Greg Donald wrote:
> > On Sat, 20 Oct 2007, Andreas S. wrote:
> > > But I think it's still a good idea to use return in order to document
> > > that the method is MEANT to return something, and that it's not just an
> > > unintended side effect.
>
> > If you want to use return, use it.  The value returned by a Ruby method
> > is t
>
> What I mean to say is the returned value is always going to be the value
> of the last evaluated expression.  Not having to use return is good.
> It's smaller code and once you get used to it, it seems very normal.
>
> --
> Greg Donald
> Cyberfusion Consultinghttp://cyberfusionconsulting.com/

The only time you need to implicitly use 'return' is when you want the
value of a variable that was processed prior to the last statement.

for example:

   y = some_method(alpha, beta)

   do_some_cleanup before returning

   return y