From: Clint Checketts <checketts@...>
Date: 2006-01-30T03:51:58+09:00
Subject: Re: nil != []

------=_Part_11050_27563360.1138560705449
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 1/29/06, Alex Polite <notmyprivateemail@gmail.com> wrote:
>
> On 1/28/06, Stefan Walk <stefan.walk@gmail.com> wrote:
> > When you get used to it, it's quite handy. Some methods return integers=
,
> > and false values on failures. If 0 was false, you'd have to distinguish
> > between 0 and false/nil when checking for success.
>

Dynamic typing in Ruby also aids the use of false =3D false and 0 =3D 0.

In Java I can't suddenly say that my variable contains a 'False' value. I
would have to make my int =3D 0 and detect the rationale behind that specif=
ic
integer. Dynamic typing solves this because myVariable =3D 5 and later it c=
an
equal 'false' when it really is false (rather than a
number that represents false)

-Clint

------=_Part_11050_27563360.1138560705449--