On Fri, 29 Sep 2017, Scott Robison wrote:
The problem is that there is no one best practice for resolving all such warnings in a way that makes all compilers happy. It is possible to fix all the warnings for one platform, then move on to the next platform and fix all its warnings, and return to the original platform and discover that new warnings have been introduced.
My own experience has been that it is possible to write valid C code which does not produce warnings at high warning levels on just about any standard C compiler. It is not necessarily a case of "whack a mole". The most annoying exception is the Microsoft Visual C Compiler, which produces deprecation warnings for standard functions.
One does need to be very careful when fixing compiler warnings so as to not introduce new bugs. The most dangerous warnings to work on are those involving signed vs unsigned types.
Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
