From: Robert Dober <robert.dober@...>
Date: 2007-01-21T18:15:06+09:00
Subject: Re: TrueClass === TrueClass

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

On 1/20/07, David Chelimsky <dchelimsky@gmail.com> wrote:
>
> On 1/20/07, Robert Dober <robert.dober@gmail.com> wrote:
> > 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 ;)
>
> Oh, you misunderstand. Let me rephrase:
>
> "How deliciously deceiving."


I was not sure, but I thought that if  you really did not realize  what was
going on I might give a hint ;)
But of course you were, sorry for the noise.

Robert


>
>


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

------=_Part_177377_5704796.1169370904200--