diff --git a/man/manual.docbook b/man/manual.docbook
index 3c2a10eb7..1c447fd06 100644
--- a/man/manual.docbook
+++ b/man/manual.docbook
@@ -11,16 +11,10 @@
Introduction
- Cppcheck is a static analysis tool for C/C++ code - it textually
- inspects your C/C++ source code to detect bugs.
-
- Cppcheck detects issues that you will not find with your compiler.
- But Cppcheck doesn't detect the types of bugs that compilers
- detect.
-
- It is our goal to generate no false positives. We always try to
- achieve 0 false positives. There will always be issues that Cppcheck fail
- to detect.
+ Cppcheck is an analysis tool for C/C++ code. Unlike C/C++ compilers
+ and many other analysis tools, we don't detect syntax errors. Cppcheck
+ only detects the types of bugs that the compilers normally fail to detect.
+ The goal is no false positives.
Supported platforms:
@@ -92,24 +86,14 @@ Checking path/file2.cpp...
Cppcheck is sure there is an
error.
- When a likely issue is discovered, Cppcheck
- bails out without reporting this issue - to prevent false positives. But
- with --all you can ensure that these issues are
+ When a likely issue is discovered Cppcheck
+ bails out without reporting this issue - to prevent false positives.
+ When --all is given, these issues are
reported.
The --all flag is useful but makes
- Cppcheck more unreliable:
-
-
-
- You will probably get false positives
-
-
-
- Cppcheck can detect issues that it can't detect by
- default
-
-
+ Cppcheck more unreliable, you will probably get false
+ positives.
Here is a simple code example:
@@ -176,6 +160,16 @@ Checking path/file2.cpp...
cppcheck --unused-functions path
+
+
+ Multithreaded checking
+
+ If you have a multicore processor, it is a good idea to use the
+ -j flag. To use 4 threads to check the files in a
+ folder:
+
+ cppcheck -j 4 path
+