[general] MSVC71 Warnings Off?
Hi all, I guess this question could have been asked before. But I've failed to find an answer from my basic search from the web so far. So please try to bear with me if it is old stuff. Our development environment is using MSVC71 at the moment, and our coding standard requires warning level 4 and 64-bit compatiblity check of the compiler. But whenever I use some of the Boost library headers (most notably Boost.Function, Boost.Integer and Boost.uBLAS for now, and we have not started using most of the other libraries yet), there are tons of warnings from the compiler. As our development team view compiler warnings as important signs of potential problems in our own code, we'd like to suppress warnings from Boost headers (assuming that they are at least better tested than our code). So my question is: Is there a way for us to suppress warnings from Boost headers without affecting the warning level significantly on our own code? Any idea is greatly appreciated. :) Cheers, Freddie -- Wu Yinghui, Freddie Research & Development Software Engineer Volume Interactions Pte Ltd 1 Kim Seng Promenade, #12-01 Great World City East Tower Singapore 237994 Tel: +65 62226962 (Ext 216) Fax: +65 62226215 Email: yhwu@volumeinteractions.com URL: http://www.volumeinteractions.com Important: This message is intended for the recipient(s) addressed above. It contains privileged and confidential information. If you are not the intended recipient, please notify the sender immediately by replying to this message and then delete it from your system. You must not read, copy, use, or disseminate this communication in any form. Thank you.
On 8/14/06, Wu Yinghui, Freddie
Hi all,
I guess this question could have been asked before. But I've failed to find an answer from my basic search from the web so far. So please try to bear with me if it is old stuff.
Our development environment is using MSVC71 at the moment, and our coding standard requires warning level 4 and 64-bit compatiblity check of the compiler. But whenever I use some of the Boost library headers (most notably Boost.Function, Boost.Integer and Boost.uBLAS for now, and we have not started using most of the other libraries yet), there are tons of warnings from the compiler.
As our development team view compiler warnings as important signs of potential problems in our own code, we'd like to suppress warnings from Boost headers (assuming that they are at least better tested than our code).
So my question is: Is there a way for us to suppress warnings from Boost headers without affecting the warning level significantly on our own code?
This will make vc++ treat a header with warning level 3:
#pragma warning(push, 3)
#include
Any idea is greatly appreciated. :)
Cheers,
Freddie
-- Wu Yinghui, Freddie Research & Development Software Engineer
Volume Interactions Pte Ltd 1 Kim Seng Promenade, #12-01 Great World City East Tower Singapore 237994 Tel: +65 62226962 (Ext 216) Fax: +65 62226215 Email: yhwu@volumeinteractions.com URL: http://www.volumeinteractions.com
Important: This message is intended for the recipient(s) addressed above. It contains privileged and confidential information. If you are not the intended recipient, please notify the sender immediately by replying to this message and then delete it from your system. You must not read, copy, use, or disseminate this communication in any form. Thank you.
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
-- Cory Nelson http://www.int64.org
Hi Freddie.
So my question is: Is there a way for us to suppress warnings from Boost headers without affecting the warning level significantly on our own code?
Any idea is greatly appreciated. :)
In our projects (also MSVC 7.1) we prepare wrapper files for
any boost headers causing such warnings that include their
respective header file, temporarily disabling the exact warning
messages. Then all other code uses those BoostWrapper header
files instead of those in boost.
It actually turns out that not many of boost header files cause these
warnings and not many different warnings at that so this is not such
a big overehead as we first expected.
I've actually been waiting for the boost 1.34 release to retest all of
our settings and report to the mailing list every one of the warnings
in question.
In case it helps anyone I've attached a packaged up part of our
source tree containing all the current BoostWrappers headers, you
might find it useful... actually there is a tiny copyright notice at the
top of each file but I did not take the time to remove it as each file
simply follows a 'include any other needed headers, disable warnings,
include header, reenable warnings' pattern... :-) so there is actually
nothing proprietary to 'copy' from there... :-)
Hope this helps...
Best regards,
Jurko Gospodnetic
begin 666 boostWrappers.rar
M4F%R(1H'`,^0
participants (3)
-
Cory Nelson -
Jurko Gospodnetic -
Wu Yinghui, Freddie