On Fri, Apr 11, 2008 at 10:36 AM, Robert J. Hansen <[EMAIL PROTECTED]> wrote: > Bob Proulx wrote: > > Always build with full warnings enabled. Always clean up warnings as > > they are introduced. Always keep a warning free build. > > > > Given the wide leeway the C and C++ standards give implementors in respect > to what is warning-worthy, I think this is crazy. There are far more > compilers in the world than just GCC, and trying to make a warning-free > build on /every/ platform is just far too much torment-of-the-damned for far > too little benefit.
Hmmm. I'd have to disagree here. I carefully consider every warning I see, and evaluate whether or not it represents a real problem. While there have been versions of various compilers in the past that like to warn about stupid things, compiler writers understand the language better than most people. If they warn me about something, then I at least give it the credit it's due. Often, these warnings indicate a real or future problem in my code. Interestingly, as my proficiency with the language (C or C++) has grown, the number of warnings I deal with has decreased. I still get errors, from stupid type-o's, but I don't get that many warnings anymore. John
