Subject: Re: [boost] Current Guidance on Compiler Warnings?
From: degski (degski_at_[hidden])
Date: 2018-11-20 07:47:48
On Tue, 20 Nov 2018 at 01:31, Emil Dotchevski via Boost <
> if you suspect that a source file contains a
> subtle bug, you could compile it with maximum linting, examine every
> warning closely, then turn it back off.
Or simply just once in a while (during dev) and walk through all those
warnings just to verify nothing is actually wrong, it least it [the
compiler] tells you where to have a look. It's now much better, but there
was a time that running the highest warning level with the VC-STL would
turn up mostly warnings in the STL.
I also used the ICC for a long time [in the past], high warning levels was
simply impossible [with the VC-STL], which gave the impression the whole
VC-STL needed a re-write [which it probably did ;-) ].
-- *âIf something cannot go on forever, it will stop" - Herbert Stein*
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk