[ntp:hackers] Quieting warnings

Harlan Stenn stenn at ntp.org
Wed Jun 3 17:40:46 UTC 2015


Folks,

I'm running different code analyzers over the codebase.

We're now at the point where there are things being done in the codebase
to quiet bogus warnings from one compiler/analyzer are reported as
warnings from a different compiler/analyzer.

Two obvious choices are:

- remove the hacks that quiet the bogus warnings

- surround these hacks with #ifdef/#endif blocks

The former means folks with various compilers will now get warnings
again, which increases our/my workload, and slightly uglifies the
codebase.

The latter means the code gets uglier and there is a greater chance for
errors to creep in.

Are there other, better choices?

-- 
Harlan Stenn <stenn at ntp.org>
http://networktimefoundation.org  - be a member!


More information about the hackers mailing list