Warnings are never harmless--they clutter the build output and introduce cognitive dissonance when trying to see if a build is clean or not.
I worked on a project where they hadn't enabled warnings during development because it was "too much trouble". When I enabled warnings, there were more than 14,000 of them, and of course then the warnings couldn't be addressed because "there were too many of them". Zero tolerance for warnings! ----- Original Message ----- From: "D. Richard Hipp" <d...@hwaci.com> To: "General Discussion of SQLite Database" <sqlite-users@sqlite.org> Sent: Tuesday, September 29, 2009 3:38 AM Subject: Re: [sqlite] Compiler warnings with Sun Studio 12.1 on Solaris 10 > > On Sep 27, 2009, at 5:28 PM, Dr. David Kirkby wrote: > >> "sqlite3.c", line 18731: warning: integer overflow detected: op >> "<<" >> "sqlite3.c", line 18748: warning: integer overflow detected: op >> "<<" > > Both cases are complaining about a constant: (0x1f<<28) Both are > harmless. > >> "sqlite3.c", line 32546: warning: statement not reached > > Complains about this code: > > /*NOTREACHED*/ > assert( 0 ); > > Harmless. > >> "sqlite3.c", line 69160: warning: integer overflow detected: op >> "<<" > > Complains about this constant: (((sqlite3_int64)1)<<63) Harmless > > All warnings are harmless and will remain unaddressed for now. > Thanks > for the reports, though! > > D. Richard Hipp > d...@hwaci.com > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
