First, I use the pre-built DLL from the SQLite web site, and then use my
compiler's library import utility to generate the appropriate import lib. 
That saves me all the warnings.

Second, examine the actual warnings, not just the count.  You'll find that
a large number of them are warnings about deprecated library methods such
as strcpy.  The fact that Microsoft has chosen to deprecate standard
library functions is a Microsoft issue rather than an SQLite issue.  It's
true that a lot of these functions are dangerous in inexperienced and
careless hands.  It's also true that they're very safe and have been used
successfully for 30 years by programmers who understand their limitations
and use them appropriately.

Examine the warnings, look at the code around them, see if there is any
merit to the warnings or if it's more of a chicken little situation.  If
you can't check all 600, spot check several which you find at random.  And
remember that there's nothing wrong with strcpy and strcat, as long as the
destination buffer is large enough for the string being received.  Look
for the allocation of that buffer and see how it's come about and how the
size is checked.

Clay Dowling

Gunnar Roth said:
> Hello,
> i want to use sqlite3 in a sub-project at work.
> when compiling with warning level 4 with vc6 ( internal philosophy ) , i
> get over 480 warnings. With warning level 3 there are still 119 left.
> This leads to problems to convince the project lead of the quality of
> sqlite3 ( which i do not doubt, as i have used it for my private project
> since some years).
> Is there any chance this warnings will be fixed sometime in the future?
> How are others dealing with this problem at work?
>
> regards,
> gunnar
>
>
>
> -----------------------------------------------------------------------------
> To unsubscribe, send email to [EMAIL PROTECTED]
> -----------------------------------------------------------------------------
>
>


-- 
Simple Content Management
http://www.ceamus.com


-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to