From: "Thomas B." <sinixlol@...>
Date: 2011-09-24T20:19:02+09:00
Subject: Re: Conditional statements with multiple arguments

Peter,

Is there a reason that something like an empty array or an empty string 
would evaluate to true as opposed to nil? Or is it just one of those 
things that just is the way it is? I guess I just don't understand the 
purpose of Ruby handling an empty array the same way as it would handle 
an array with a given value. Wouldn't it just be easier to have the 
empty array evaluate to nil like this:

array = []

puts array.nil? # returns => true (it actually returns false, because as 
you said, it isn't nil or false)

array = [1, 2]

puts array.nil? # returns => false

I know we're getting a little bit into the bushes with this stuff, and I 
should probably be a little bit more resourceful. It's just interesting 
to me that an empty array or string would evaluate to a true statement.

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