Subject | Re: [ib-support] gpre and VisualC++ |
---|---|
Author | Eric Boyajian |
Post date | 2001-06-01T16:04:29Z |
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
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)
Eric Boyajian
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
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)
Eric Boyajian