walkero
/
cppcheck
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

Manual: minor tweaks. remark that it is not certain that fixing 'performance' messages will have a positive effect on the speed. and in general it doesn't make the code more readable.

This commit is contained in:
Daniel Marjamäki 2010-12-09 20:13:02 +01:00
parent 9de016b96d
commit 9c81695c12
1 changed files with 5 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
man/manual.docbook
View File

@ -5,7 +5,7 @@
<bookinfo> <bookinfo>
<title>Cppcheck 1.46</title> <title>Cppcheck 1.46</title>
<date>2010-12-03</date> <date>2010-12-09</date>
</bookinfo> </bookinfo>
<chapter> <chapter>
@ -150,14 +150,10 @@ Checking path/file2.cpp...
</varlistentry> </varlistentry>
</variablelist> </variablelist>
<remark>The focus of <literal>Cppcheck</literal> development is to <remark>The performance messages are based on 'common knowledge'. It is
detect bugs, <literal>Cppcheck</literal> is not a not certain that fixing performance messages will make any measurable
style-checker.</remark> difference in speed. Fixing performance messages generally doesn't make
your code more readable.</remark>
<remark> Cppcheck doesn't try to detect hotspots so fixing
<literal>performance</literal> messages might have no measurable
difference. Fixing performance messages doesn't make your code more
readable.</remark>
</section> </section>
<section> <section>