A brief note about MISRA

We are often asked whether the PVS-Studio analyzer supports MISRA standard. I decided to write a short note to make it easy to answer the letters, giving the link. A brief answer - we do not currently support standards MISRA C, MISRA C++ and do not plan to do that. Here is a detailed explanation of our position concerning this question.

We have never focused on the support of the MISRA C, MISRA C++ and other related standards. We are aimed at searching real bugs, not the prevention of potential problems by limiting programmers.

For example, we don't induce the programmers to write break in swicth, and don't prohibit using goto. We think there is little use in the recommendation of using // comment instead of /* */. We also don't see the point to warn C programmers that they have address arithmetic p++ in their program.

Such diagnostics bulk up the analyzer output and instead of searching for real errors, a person starts fighting with thousands theoretically good, but having no influence suggestions of the code improvement.

We have chosen a different path. None of the standards says, "avoid typos". Still, everybody makes typos. Our analyzer is very helpful in this regard. For example V501 diagnostic itself is a great way to protect against them. Such diagnostics are our competitive advantage.

Yes, we can partly take something from MISRA. This means that some things are definitely useful and at the same time appear in different standards and analyzers.

At this time we do not plan to support MISRA. We understand that some programmers may need to support this standard. But we don't want to clutter up the analyzer. And I think that's OK. If there is a need for the code to comply with the MISRA standard, there are plenty of tools that allow doing that.

Analyzers that check the compliance of the code with the MISRA standard:

• Coverity by Synopsys
• Klocwork by Rogue Wave Software
• LDRA Testbed by Liverpool Data Research Associates
• Parasoft C/C++test by Parasoft
• PC-Lint by Gimpel Software
• Polyspace by MathWorks
• QA-C by Programming Research
• Understand by SciTools
• and so on

As you see, there are many tools, able to give recommendations about writing more qualitative code.

If you want to search for real errors, then that's our task!

Demonstration of PVS-Studio abilities in the detection of REAL bugs in the code:

• Errors found in Open Source projects (at the time of writing this article, we have already more than 10500 errors).
• Articles about the check of well-known open source projects with the help of PVS-Studio.