From: Robert Dober <robert.dober@...>
Date: 2007-01-21T02:10:20+09:00
Subject: Re: TrueClass === TrueClass

------=_Part_172433_11757225.1169313018741
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 1/19/07, David Chelimsky <dchelimsky@gmail.com> wrote:
>
> On 1/19/07, Vincent Fourmond <vincent.fourmond@9online.fr> wrote:
> > Bojan Mihelac wrote:
> > > Hi all,
> > > why is:
> > >
> > > TrueClass === TrueClass # false
> > > Object === Object # true
> > >
> > > Documentation states that === method is used to provide meaningful
> > > semantic in case statements. Can anyone explain me why some classes
> > > returns false?
> >
> >   === returns true with one class if you 'compare' it to an instance of
> > the class:
> >
> > irb(main):002:0> TrueClass == TrueClass
> > => true
> > irb(main):003:0> TrueClass === TrueClass
> > => false
> > irb(main):004:0> TrueClass === true
> > => true
> >
> >   Cheers,
>
> Ah - so Object === Object returns true because the second Object is an
> instance of the first Object. How deceiving.


If you are looking for a language in which not everything is an object,
there are plenty around ;)

>
> >         Vince
> >
> > --
> > Vincent Fourmond, PhD student
> > http://vincent.fourmond.neuf.fr/
> >
> >
>
> Robert


-- 
"The best way to predict the future is to invent it."
- Alan Kay

------=_Part_172433_11757225.1169313018741--