On Sat, 19 Jul 2003 14:58:51 +0900
"Kurt M. Dresner" <kdresner / cs.utexas.edu> wrote:

> When I learned python I was overjoyed that I could evaluate 1 < 2 < 3
> and get "true".  I just realized that you can't do that in Ruby.  Is
> there a reason why?  Is it good?  I know I can use "between", but
> still...

http://www.rubygarden.org/article.php?sid=286

So basically, it's because it's hard to implement, even more so because
true/false/nil are singleton objects. (So you can't, for instance, save state
in a particular instance of 'true', because there's only one.)

Jason Creighton