C++ compiler warnings are extremely helpful to prevent software bugs from the beginning on. Sadly, most warnings are either undetected or not shown by the current warning level. This repo checks the warning coverage of your C++ compiler with 68 test cases (see the .cpp files in the 📂test_cases folder).
Requires cmake and a C++ compiler installed. Then execute in a terminal window:
> git clone https://github.com/fleschutz/CWTS # or download and unzip the ZIP file (click the green button)
> cd CWTS
> cmake .
> make -k # option '-k': keep going, even on errors
Expect a lot of compiler warnings but the more warnings the better! Edit CMakeLists.txt before to force using a certain C++ compiler.
Each test case (or .cpp file) compiled without warnings or errors is a miss. And the winner is:
- clang-tidy 10.0 which misses 8 warnings only.
- Clang 10.0.0 which misses 11 warnings.
- GCC 9.3.0 which misses 14 warnings.
- Visual Studio 2019 which misses 17 warnings.
- Visual Studio 2017 which misses 19 warnings.
- Cppcheck 2.11 which misses 23 warnings.
See the 📂test_results folder for details and older versions. Note: all results with highest warning level enabled (see below).
Please note every compiler sets the default warning level to 'normal', whatever this means. And each one supports different options to be more pedantic:
| Compiler | Options | Comment |
|---|---|---|
| Clang | -Weverything -pedantic |
|
| clang-tidy | -checks=*,-modernize* |
hints how to modernize the code are switched off |
| Cppcheck | --enable=all |
|
| GCC | -Wall -Wextra -pedantic -Wundef |
-Wall and -Wextra do not enable all warnings! To keep backwards compatibility, -Wall is basically, "All warnings as of 1990." -Wextra covers a lot of the newer warnings, but still misses a few. |
| Visual Studio | /Wall |
This means your project is compiled with the highest warning level and zero compiler warnings are acceptable.
Introducing the Zero Warnings Policy by enabling the highest warning level often results in hundreds or even thousands of warnings. To get started you may want to begin with a lower warning level first. Now, fix those warnings and gradually dial up the warning level.
As soon as there are no more warnings turn warnings into errors to enforce the Zero Warnings Policy from now on. That way warnings can no longer be ignored because the build fails. The corresponding compiler options are -Werror for Clang and GCC and /WX for Visual Studio.
Dear API developers: introducing the Zero Warnings Policy heavily depends on the header files being used. Please make sure your header files do not produce any compiler warnings!
Send your email feedback to: markus.fleschutz [at] gmail.com
This open source project is licensed under the CC0 license. All trademarks are the property of their respective owners.