[ntp:hackers] Quieting warnings

Martin Burnicki martin.burnicki at burnicki.net
Thu Jun 4 08:18:07 UTC 2015


Danny Mayer wrote:
> I have a lot of experience with this when migrating code to Windows. My
> preference is to see all warnings during the compile time and figure out
> what the reason was for the warning and fix it. It's takes a lot of
> effort and consideration and when you fix the warning you need to make
> sure it's the right fix otherwise when other compilers build the
> resulting source code it will start issuing new warnings. The work
> needed is tedious and lengthy but the results are worth it. It's always
> amazing that some compilers miss some issues and find others and then a
> newer version of the compiler comes along and finds something else.
>
> I usually work to get rid of EVERY warning for a given compiler version
> before I consider it good. That does nothing for whether or not the code
> is good and does the right thing but when you have to do the work you
> need to take the time to understand what each piece is doing so that the
> fix is correct. I never suppress compiler warnings.

I absolutely agree.

Martin



More information about the hackers mailing list