VC ++ 2010：用/ Wall编译

Question

I'd like to compile my project with /Wall.

When I do this I get tons of warning from third-party code (boost libraries, other system header files). The only place where I include these third-party header files is in my precompiled header ( stdafx.h ).

I tried this (in stdafx.h )

#pragma warning(push,3)
    // include all the third-party headers here
#pragma warning(pop)

to compile all third-party code with warning level 3.

However I still get hundreds of warnings from files like math.h , xmemory , vector , string_generator.hpp (boost.uuid), placeholders.hpp (boost.asio), ...

How can I make sure to compile all third-party code with warning level 3 while compiling my own code with all warnings enabled?

Answer 1

3rd party code is modified less frequently, so it's a good idea to have all these includes in your StdAfx.h and then your above solution would suppress their warnings.

Either that or create some other wrapper header files that use the above pragma around the actual includes to the libraries you use.

I can't think of a third way. I say shove them all in the stdafx ( and where they're actually included, too. remember that stdafx is an optimization - not a replacement for careful selective including within your source files)

Answer 2

/W4 is more realistic than /Wall. I routinely use stl, tr1, and windows headers with /W4. I don't know about boost.

The reason wrapping the headers with the #pragma isn't enough is that some of the warnings are generated when instantiating templates or expanding macros (or perhaps even with inlining).

Answer 3

Check all of the includes that your files pull in. It may be that one of them likely resets warnings to their default state. I've seen this with either MFC or ATL headers that come with VC++ - some warnings are disabled and then re-enabled with a "default" call specifier rather than using a push/pop pair.