Our website uses cookies to enhance your browsing experience.
Accept
to the top
close form

Fill out the form in 2 simple steps below:

Your contact information:

Step 1
Congratulations! This is your promo code!

Desired license type:

Step 2
Team license
Enterprise license
** By clicking this button you agree to our Privacy Policy statement
close form
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
* By clicking this button you agree to our Privacy Policy statement

close form
Free PVS‑Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

close form
To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

close form
I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

close form
check circle
Message submitted.

Your message has been sent. We will email you at


If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

>
>
Comparing Analysis Capabilities of PVS-…

Comparing Analysis Capabilities of PVS-Studio and Visual Studio 2015's Analyzer

Apr 25 2015

In one of the articles at Visual C++ Team Blog, the developer team were discussing the static code analyzer that would ship with Visual Studio 2015. According to their data, there will be no difference in the static analysis capabilities between Visual Studio 2013's and Visual Studio 2015's versions.

0319_VS2015/image1.png

Here's an excerpt from the article "C/C++ Code analysis in VS2015":

Let's start with what has not changed.

  • Code analysis is still available in all editions of Visual Studio just like how it was in VS2013.
  • No additional checkers added between VS2013 and VS2015.

It means that Visual Studio 2015's analyzer will be absolutely the same as the previous version regarding its functionality. We already carried out a comparison of the PVS-Studio analyzer and the analyzer integrated into Visual Studio 2013 - see the corresponding article. Therefore, the old data are still relevant. See Table 1 to know the number of errors found by these analyzers in a suit of test projects.

0319_VS2015/image2.png

Table 1 - Comparison of the analyzers' diagnostic capabilities

The difference between the two tools is quite prominent: 77% and 12% are pretty different figures, aren't they? Perhaps this difference has grown even bigger today as we constantly add new diagnostics into PVS-Studio.

Popular related articles


Comments (0)

Next comments next comments
close comment form