Re: [boost] Misuse of warnings-as-errors?

Subject: Re: [boost] Misuse of warnings-as-errors?
From: Rob Stewart (robertstewart_at_[hidden])
Date: 2014-05-01 18:26:50

On May 1, 2014 12:52:51 PM EDT, John Maddock <boost.regex_at_[hidden]> wrote:
>>
>> I see several places in the bug tracking system where people complain
>about compiler warnings and are told that fixing that sort of thing is
>completely ridiculous and the bugs are closed as “won't fix”.
>>
>> But then warnings-as-errors is enabled in several places –
>libs/pool/test, libs/type_traits/test, libs/units/test, etc.
>>
>> Shouldn’t boost have one or the other?
>
>Personally, I like my stuff to be warning free, and in something as 
>"core" as type_traits, any warning at all can be a real pain that gets 
>repeated dozens of times each with 10 pages of instantiation
>back-trace, 
>so I think it makes sense to enforce a no-warnings policy in that one 
>case.  

+1

___
Rob

(Sent from my portable computation engine)