Here examples of all 3, all from the same source file and the same code block:
C:\SQLite\SourceWin\loadext.c(138) : warning C4047: 'initializing' : 'int (__cdecl *)(struct sqlite3_stmt *,int )' differs in levels of indirection from 'const char *(__cdecl *)(struct sqlite3_stmt *,int )' const sqlite3_api_routines sqlite3_apis = { sqlite3_column_double, C:\SQLite\SourceWin\loadext.c(125) : warning C4113: 'int (__cdecl *)(struct sqlite3 *,void *,void (__cdecl *)(void *,struct sqlite3 *,int ,const char *))' differs in parameter lists from 'int (__cdecl *)(struct sqlite3 *)' const sqlite3_api_routines sqlite3_apis = { sqlite3_collation_needed, C:\SQLite\SourceWin\loadext.c(208) : warning C4133: 'initializing' : incompatible types - from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl *)(void *,int ,const char *,const char *,__int64 ),void *)' to 'char *(__cdecl *)(int ,char *,const char *,... )' const sqlite3_api_routines sqlite3_apis = { sqlite3_update_hook, This codeblock ends like this: /* ** The original API set ends here. All extensions can call any ** of the APIs above provided that the pointer is not NULL. But ** before calling APIs that follow, extension should check the ** sqlite3_libversion_number() to make sure they are dealing with ** a library that is new enough to support that API. ************************************************************************* */ sqlite3_overload_function, }; RBS -----Original Message----- From: Joe Wilson [mailto:[EMAIL PROTECTED] Sent: 24 February 2007 17:29 To: sqlite-users@sqlite.org Subject: RE: [sqlite] compiling with VC++ They're probably harmless. Even so, can you post the file name/line of one example of each of the following 3 warnings as they seem odd: warning C4047: 'initializing' : '__int64 (__cdecl *)(struct Mem *)' differs in levels of indirection from 'char *(__cdecl *)(const char *,char *)' warning C4113: '__int64 (__cdecl *)(struct Mem *)' differs in parameter lists from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl *)(void *,int ,const char *,const char *,__int64 ),void *)' warning C4133: 'initializing' : incompatible types - from '__int64 (__cdecl *)(struct sqlite3_stmt *,int )' to 'double (__cdecl *)(struct sqlite3_stmt *,int )' --- RB Smissaert <[EMAIL PROTECTED]> wrote: > When compiling this source code I get 265 warning, which doesn't really > worry me that much as it all seems to be working fine, but in general what > kind of warning should be taken seriously? > > I only have 8 different types of warnings: > > warning C4018: '!=' : signed/unsigned mismatch > warning C4028: formal parameter 1 different from declaration > warning C4047: 'initializing' : '__int64 (__cdecl *)(struct Mem *)' differs > in levels of indirection from 'char *(__cdecl *)(const char *,char *)' > warning C4090: 'function' : different 'const' qualifiers > warning C4113: '__int64 (__cdecl *)(struct Mem *)' differs in parameter > lists from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl *)(void *,int > ,const char *,const char *,__int64 ),void *)' > warning C4133: 'initializing' : incompatible types - from '__int64 (__cdecl > *)(struct sqlite3_stmt *,int )' to 'double (__cdecl *)(struct sqlite3_stmt > *,int )' > warning C4244: '+=' : conversion from '__int64 ' to 'int ', possible loss of > data > warning C4761: integral size mismatch in argument; conversion supplied ____________________________________________________________________________ ________ Looking for earth-friendly autos? Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/ ---------------------------------------------------------------------------- - To unsubscribe, send email to [EMAIL PROTECTED] ---------------------------------------------------------------------------- - ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------