Boost logo

Boost :

Subject: Re: [boost] Misuse of warnings-as-errors?
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2014-05-01 13:06:19

> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Chris Cooper
> Sent: 01 May 2014 17:24
> To: boost_at_[hidden]
> Subject: [boost] Misuse of warnings-as-errors?
> 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
> 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
> 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
> anywhere?

In an ideal world yes, blizzards of warnings are a PITA, but ...

It often is isn't that simple, and a thankless task.

I think the consensus is that if you enforce warnings-as-errors, then you are on
your own.

You may be able to do it, but if not, then tough. We did our best but ...


Paul A. Bristow
Prizet Farmhouse
Kendal UK LA8 8AB
+44 01539 561830

Boost list run by bdawes at, gregod at, cpdaniel at, john at