On 01/05/14 18:34, Andrey Semashev wrote:
On Thursday 01 May 2014 16:23:48 Chris Cooper wrote:
I’m pretty new to boost, but I’m sensing a desire to have cake and eat it too … correct me if I’m wrong of course!
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? Either warnings are important enough to treat them as errors in the unit tests (in which case they should get fixed) or else they’re not that important and warnings-as-errors shouldn’t be enabled by default anywhere?
This is basically each library's choice, there's no common requirement. Personally I think that trying to work around all warnings in code is a rather pointless and even detrimental thing to do.
Every library author should make a reasonable attempt that correct code involving usage of their library does not generate warnings.