On 4/29/26 13:34, Andrey Semashev via Boost wrote:
This topic has been beaten many times, but in short, compiler warnings are not portable and are often bogus and/or subjective.
The obvious counterargument to this is that if you disagree with a warning, you should disable it. There's no point in the compiler generating warnings if you're just going to ignore them, piles of bogus warnings only make it more difficult to find the warnings you actually care about. I've recently started experimenting -Werror, mainly because my build process produces so much output that I'm likely to miss warnings entirely if I don't treat them as errors. The obvious problem with this approach is third party libraries that produce warnings, which is all the more reason for library authors to to keep their libraries completely warning-free. -- Rainer Deyke - rainerd@eldwood.com