From 64578e803155cffec40b0d1ddbb83a017f106be0 Mon Sep 17 00:00:00 2001 From: Gluttton Date: Sun, 21 May 2017 22:48:29 +0300 Subject: [PATCH] Added suggestions for usage of cppcheck: use --check-config, use -j1 for detection of unused functions, use --force for checking all #ifdef. --- 02-Use_the_Tools_Available.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/02-Use_the_Tools_Available.md b/02-Use_the_Tools_Available.md index a6e4a1f..fd62558 100644 --- a/02-Use_the_Tools_Available.md +++ b/02-Use_the_Tools_Available.md @@ -167,7 +167,7 @@ The best bet is the static analyzer that you can run as part of your automated b [PVS-Studio](http://www.viva64.com/en/pvs-studio/) is a tool for bug detection in the source code of programs, written in C, C++ and C#. It is free for personal academic projects, open source non-commercial projects and independent projects of individual developers. It works in Windows and Linux environment. ### Cppcheck -[Cppcheck](http://cppcheck.sourceforge.net/) is free and open source. It strives for 0 false positives and does a good job at it. Therefore all warnings should be enabled: `--enable=all` +[Cppcheck](http://cppcheck.sourceforge.net/) is free and open source. It strives for 0 false positives and does a good job at it. Therefore all warnings should be enabled: `--enable=all`. For correct work it requires well formed path for headers, so before usage don't forget pass: `--check-config`. If you try to found unused functions don't use `-j` with more than 1. Remember to add `--force` for code with a lot number of `#ifdef` if you need check all of them. ### Clang's Static Analyzer