At 09:04 AM 6/1/2001 -0700, Eric Boyajian wrote:

>Couple of comments regarding gpre:
>
>1. I have found that the C code that it generates sometimes causes type
>mismatch compiler warnings in VC++. After running gpre, I run short perl
>scripts on the .c files to add the needed explicit casts.
>
>Example: ibase.h contains
> #define blr_end 255
> yet blr_end is used as an argument that is expected
> to be of type char in gpre generated code

Yup. At the time it was written, a char was assumed to be unsigned,
and that passed all the compilers around then. Doesn't any more.
That's in line to be fixed in firebird.

>2. gpre generates API function calls that cannot be found in the
>documentation.
>Examples: isc_compile_request2
> isc_start_and_send
> isc_embed_dsql_* (about six such related functions)

In their wisdom, Borland decided that documenting the whole API was
unnecessary.


Regards,

Ann
www.ibphoenix.com
We have answers.