On Sat, Jan 5, 2013 at 11:29 PM, Joel Pearson <lists / ruby-forum.com> wrote:

> There's only one time I can think of where I use "or" for the sake of
> readability. I'll often have a main method call a series of other
> methods, each of which returns a boolean, and sets the error level as a
> way of reporting failure. That is then passed to the errorhandler. This
> leads to some simple lines like this:
>
> boolean_return_method or fail

There is already too much written about using return values for error
handling.  So I'll only say that I don't think this kind of design is
good.

Kind regards

robert

-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/