In general, boolean expressions should return boolean values
(yes,no,true,false).  This is a bug.

Paul Kenney
[EMAIL PROTECTED]
916-212-4359

> -----Original Message-----
> From: Samuel R. Neff [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 20, 2004 1:20 PM
> To: CF-Talk
> Subject: RE: Is it a bug or not a bug?
>
>
> "and" is a boolean operator.  I would expect the result to always be a
> boolean.
>
> In my opinion, it's a bug.
>
> Sam
>
>
>
> ----------------------------------------
> Blog http://www.rewindlife.com
> TeamMM http://www.macromedia.com/go/team
> ----------------------------------------
>
>
> > -----Original Message-----
> > From: Jerry Johnson [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, April 20, 2004 4:15 PM
> > To: CF-Talk
> > Subject: Re: Is it a bug or not a bug?
> >
> > >>> [EMAIL PROTECTED] 04/20/04 03:55PM >>>
> > <snip>
> > >Interesting. I would have guessed that both sets would have
> > returned the
> > >same exact results. That, to me, is indeed a bug.
> >
> > Dave,
> >
> > Could you explain why you are sure this is a bug, and not
> > just an unexpected casting issue?
> >
> > Why should #1 and 20# automatically output 1?
> >
> > You are anding a boolean and an integer, and getting an integer out.
> >
> > I think it would be a bug if it produced different results
> > each time it was called. But it seems to be behaving
> > predictably. Which to me means it is not a bug.
> >
> > Curious,
> > Jerry Johnson
>
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to