Daniel,

I've started to go through IBO to remove potential ambiguities. This is a
massive undertaking. I am pretty sure IBO has worked as I expected, but it
is the potential of ambiguity I see and I want to eliminate it. Future
versions of the compiler may behave differently. Better to lock things down
now than wait for a problem.

Are you aware of any compiler settings that could affect this?
Have there been any inconsistencies with the compiler on this already?

Thanks for pointing this out.

Regards,
Jason Wharton

> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
> Behalf Of Daniel Rail
> Sent: Thursday, May 11, 2006 2:31 AM
> To: IBObjects@yahoogroups.com
> Subject: Re: [IBO] IBOQuery Locate bug IBO 4.6A
>
>
> Hi,
>
> At May 10, 2006, 8:39 PM, Jason Wharton wrote:
>
> > I've gone ahead and added in the parenthesis.
> > It seems odd to me that this could make a difference.
>
> It's possible that the compiler might have interpreted the line:
> if not Prepared or not SQLIsValid then
>
> like this:
> if not (Prepared or not SQLIsValid) then
>
> instead of:
> if (not Prepared) or (not SQLIsValid) then
>
> As, most people might have expected. I had the same odd behavior just
> recently in one of my applications that I'm working on. And, that was
> in my own code, not IBO.
>
> --
> Best regards,
> Daniel Rail
> Senior System Engineer
> ACCRA Group Inc. (www.accra.ca)
> ACCRA Med Software Inc. (www.filopto.com)