OK, when I do instead of commenting those lines out: 0, //sqlite3_last_insert_rowid,
Etc. I get less warnings. Got 143 now instead 265 and no more Warnings of the type C4028 and nil anymore in the .c file loadext.c So, that looks much better. Is it OK though to do this: 0, //sqlite3_libversion, 0, //sqlite3_libversion_number, Or should I put something different than that zero, like an empty string? If so how do I do that in C? It looks then that although it compiled and worked those instructions from Tod Tanner weren't quite right then. RBS -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 24 February 2007 20:06 To: sqlite-users@sqlite.org Subject: Re: [sqlite] compiling with VC++ "RB Smissaert" <[EMAIL PROTECTED]> wrote: > All C4028 warnings originate from this code block: > > const sqlite3_api_routines sqlite3_apis = { [...] > sqlite3_busy_timeout, > //sqlite3_changes, > //sqlite3_close, > sqlite3_collation_needed, > sqlite3_collation_needed16, > > Not sure it is relevant but some lines are commented out to do with making > it VB compatible. > Yes, it is relevant. Commenting out those lines breaks the code in a big way. If that module is given you problems, why don't you compile with -DSQLITE_OMIT_LOAD_EXTENSION=1 to leave it out. -- D. Richard Hipp <[EMAIL PROTECTED]> ---------------------------------------------------------------------------- - To unsubscribe, send email to [EMAIL PROTECTED] ---------------------------------------------------------------------------- - ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
