numbers to determine a bit value?
....tony
r e v o l u t i o n w e b d e s i g n
[EMAIL PROTECTED]
www.revolutionwebdesign.com
its only looks good to those who can see bad as well
-anonymous
-----Original Message-----
From: Barney Boisvert [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 11, 2004 7:01 PM
To: CF-Talk
Subject: RE: Boolean Inconsistency
But it's not changing the values, it's only coercing them as much as it
needs for evaluation. Not like a function call that returns boolean.
It one of the little bits of weirdness that are present in loosely-typed
languages.
Cheers,
barneyb
> -----Original Message-----
> From: Scott Brady [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 11, 2004 3:45 PM
> To: CF-Talk
> Subject: RE: Boolean Inconsistency
>
> Original Message:
> > From: "Barney Boisvert" <[EMAIL PROTECTED]> Actually, I
> > think what's happening is CF is returning the
> value of the last
> > evaluated portion of the _expression_. In the first, both
> need evaluation, so
> > we return 3, the second one. If the second, only the first
> needs evaluation
> > (becase we know the _expression_ can't be true if either part
> is false), so
> > false is returned.
> >
> > That's just a guess though.
>
> Looks like that was a good guess. I tried swapping it to be
> #(3 and True)# and it does display true.
>
> So, that explains what it does. It sure doesn't explain why.
> That just seems retarded. It seems like it should return the
> boolean result, and not "whatever was last evaluated".
>
> Thanks!
>
> Scott
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
