popov wrote:
>>And in other cases the
>>warning cannot be eliminating without code duplication, which you would have
>>noticed when compiling reasonably complex template code and getting tons of
>>unused variable or argument warnings...
> 
> You probably do not have to fix warnings if you know these are harmless.
> However, it is worth to ONCE look at ALL possible warnings the compiler is
> able to tell you. Therefore: turn them on.

I have a long list of warnings for various compilers I never care about 
because they are just bogus as they are for inexperienced programmers.  Or 
they are portability information that is plain wrong when dealing with 
conforming compilers rather than ancient junk compilers.

The best example is POV-Ray: If you were to "fix" the warnings you get with 
all warnings enabled, you are going to seriously damage the code.  This 
actually happened a while back when someone had the idea to "fix all warnings".

	Thorsten

Post a reply to this message