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

manual: updated the Severities chapter. No major changes, just tried to make it more clear.

This commit is contained in:
Daniel Marjamäki 2013-01-11 18:35:37 +01:00
parent 7e61d1f2da
commit b5dba75c3f
1 changed files with 6 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
man/manual.docbook
View File

@ -147,7 +147,9 @@ Checking path/file2.cpp...
<term>performance</term> <term>performance</term>
<listitem> <listitem>
<para>suggestions for making the code faster</para> <para>Suggestions for making the code faster. These suggestions are
only based on common knowledge. It is not certain you'll get any
measurable difference in speed by fixing these messages.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -155,7 +157,8 @@ Checking path/file2.cpp...
<term>portability</term> <term>portability</term>
<listitem> <listitem>
<para>portability warnings. 64-bit portability. code might work different on different compilers. etc.</para> <para>portability warnings. 64-bit portability. code might work
different on different compilers. etc.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -163,16 +166,10 @@ Checking path/file2.cpp...
<term>information</term> <term>information</term>
<listitem> <listitem>
<para>Informational messages that might be interesting. Ignore <para>Informational messages about checking problems.</para>
these messages unless you really agree.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
</variablelist> </variablelist>
<remark>The performance messages are based on 'common knowledge'. It is
not certain that fixing performance messages will make any measurable
difference in speed. Fixing performance messages generally doesn't make
your code more readable.</remark>
</section> </section>
<section> <section>