2020-07-22 14:31:02 +02:00
< html >
< head >
< title > Severities< / title >
< / head >
< body >
< h1 > Severities< / h1 >
< h2 > error< / h2 >
< img src = "images/severities-error.png" > < br >
2020-07-23 16:09:24 +02:00
< p > when code is executed there is some bad behavior (undefined behavior, leak)< / p >
2020-07-22 14:31:02 +02:00
< h2 > warning< / h2 >
< img src = "images/severities-warning.png" > < br >
2020-07-23 16:09:24 +02:00
< p > when code is executed there might be undefined behavior< / p >
2020-07-22 14:31:02 +02:00
< h2 > style< / h2 >
< img src = "images/severities-style.png" > < br >
2020-07-23 16:09:24 +02:00
< 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 >
2020-07-22 14:31:02 +02:00
< h2 > performance< / h2 >
< img src = "images/severities-performance.png" > < br >
2020-07-23 16:09:24 +02:00
< 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 >
2020-07-22 14:31:02 +02:00
< h2 > portability< / h2 >
< img src = "images/severities-portability.png" > < br >
2020-07-23 16:09:24 +02:00
< p > portability warnings. Implementation defined behavior. 64-bit portability. Some undefined behavior that probably works " as you want" . etc.< / p >
2020-07-22 14:31:02 +02:00
< h2 > information< / h2 >
< img src = "images/severities-information.png" > < br >
2020-07-23 16:09:24 +02:00
< p > Configuration problems. If you get such output then your code is ok but your cppcheck configuration could be improved.< / p >
2020-07-22 14:31:02 +02:00
< / body >
< / html >
