Subject: [boost] Misuse of warnings-as-errors?
From: Chris Cooper (chris.cooper_at_[hidden])
Date: 2014-05-01 12:23:48
Im pretty new to boost, but Im sensing a desire to have cake and eat it too
correct me if Im 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.
Shouldnt 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 theyre not that important and warnings-as-errors shouldnt be enabled by default anywhere?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk