From: Brian Candler <b.candler@...>
Date: 2010-11-04T22:40:05+09:00
Subject: Re: true! or false!

Thomas Sawyer wrote in post #959291:
> If only the error message could say something about WHAT was not true
> or false, this could be pretty nifty.

You could override the exception message:

class TrueClass
  def false!(err = "not false!")
    raise err
  end
end

(1 == 2).false! "Maths is broken"

You end up with something like dfect, just with different ordering of 
the values.

-- 
Posted via http://www.ruby-forum.com/.