$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [boost] policy on compiler warnings?
From: Kenny Riddile (kfriddile_at_[hidden])
Date: 2009-06-20 20:03:57
Kenny Riddile wrote:
> Does Boost have any documented policy on compiler warnings?  I, like a 
> lot of people, use warning level 4 when compiling with MSVC.  I also 
> usually turn on warnings as errors, but I cannot easily do that since 
> many Boost libraries emit warnings at warning level 4 under MSVC9.  I 
> realize that warnings aren't really standardized across compilers, but I 
> would still expect a project that touts itself as "...one of the most 
> highly regarded and expertly designed C++ library projects in the 
> world." to strive for zero warnings under a commonly used setting on one 
> of its official test compilers.  I have created the following tickets 
> regarding warnings that are currently causing me trouble:
> 
> https://svn.boost.org/trac/boost/ticket/3193
> https://svn.boost.org/trac/boost/ticket/3194
> https://svn.boost.org/trac/boost/ticket/3195
> https://svn.boost.org/trac/boost/ticket/3196
> https://svn.boost.org/trac/boost/ticket/3197
> 
> Thanks,
> Kenny Riddile
> 
> _______________________________________________
> Unsubscribe & other changes: 
> http://listarchives.boost.org/mailman/listinfo.cgi/boost
> 
and another:
https://svn.boost.org/trac/boost/ticket/3198
Apparently some prior attention has been given to suppressing warnings 
specific to warning level 4 under MSVC...line 1139 of lexical_cast.hpp 
describes working around such a warning (and then ignores the 
unreachable code warning emitted a few lines down).