Subject: Re: [boost] Misuse of warnings-as-errors?
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2014-05-01 12:34:36
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.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk