forked from danmar/cppcheck
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathseverities.html
47 lines (33 loc) · 1.31 KB
/
severities.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
<html>
<head>
<title>Severities</title>
</head>
<body>
<h1>Severities</h1>
<h2>error</h2>
<img src="images/severities-error.png"><br>
<p>when code is executed there is some bad behavior (undefined behavior, leak)</p>
<h2>warning</h2>
<img src="images/severities-warning.png"><br>
<p>when code is executed there might be undefined behavior</p>
<h2>style</h2>
<img src="images/severities-style.png"><br>
<p>point out possible mistakes, and suggest more defensive programming. Examples:
<ul>
<li>unused code/variables/functions
<li>conditions that are always true/false
<li>constness
<li>operator precedence
</ul>
</p>
<h2>performance</h2>
<img src="images/severities-performance.png"><br>
<p>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.</p>
<h2>portability</h2>
<img src="images/severities-portability.png"><br>
<p>portability warnings. Implementation defined behavior. 64-bit portability. Some undefined behavior that probably works "as you want". etc.</p>
<h2>information</h2>
<img src="images/severities-information.png"><br>
<p>Configuration problems. If you get such output then your code is ok but your cppcheck configuration could be improved.</p>
</body>
</html>