On 29 Apr 2026 12:16, Dennis Luehring via Boost wrote:
Am 29.04.2026 um 11:02 schrieb Andrey Semashev via Boost:
Personally, I never use -Werror and don't consider this a good practice.
rational for this? does it forces too much that people try to prevent warnings at any cost/without thinking about?
This topic has been beaten many times, but in short, compiler warnings are not portable and are often bogus and/or subjective. Even within the same compiler line, one version may not generate a warning and the next one will, for the same code. Requesting the compiler to fail in these conditions is counter-productive and hostile towards users. As a user, I have to deal with a number of libraries used in my projects. Some of these libraries enforce -Werror. And almost always this causes problems for me because, of course, compilation fails because of warnings on the target platforms I use. Some libraries are generous enough to allow me disable warnings-as-errors. Others I have to patch and then maintain the patches myself. The best case scenario is the build passes because it doesn't emit warnings and I don't have to do anything, but even then -Werror doesn't give me anything, as a user.