Boost logo

Boost :

Subject: Re: [boost] Towards a Warning free code policy proposal
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2010-08-30 15:07:21


----- Original Message -----
From: "Roland Bock" <rbock_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Monday, August 30, 2010 8:32 PM
Subject: Re: [boost] Towards a Warning free code policy proposal

>
> On 08/27/2010 06:26 PM, vicente.botet wrote:
>> I propose to extend this to a 2-level enabling warning system
>>
>> BOOST_ENABLE_WARNINGS: If defined, enable warnings for all the Boost libraries
>> BOOST_<LIB>_ENABLE_WARNINGS: If defined, enable warnings for a specific library<LIB>
>>
>>
>>
> Switch the logic and I might agree:
>
> BOOST_DISABLE_WARNINGS: If defined, disable warnings for all the Boost libraries
> BOOST_<LIB>_DISABLE_WARNINGS: If defined, disable warnings for a specific library<LIB>

I proposed the enabling one as Boost.Exception writen by Andrey Semashev use already this pattern.

Anyway, I agree that disabling provides to the user the same functionality and favor the warning tracking. SO +1 for the switch.

Vicente


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk