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.

>
>
OOO "Program Verification Systems&…

OOO "Program Verification Systems" announces the issue of a new version of the static code analyzer - Viva64 2.30

Apr 20 2009
Author:

OOO "Program Verification Systems" announces the issue of a new version of the static code analyzer - Viva64 2.30. Viva64 tool is designed for searching errors in the code of 64-bit applications and for their performance increase.

Now the code analyzer will help the developers in optimizing the size of RAM used by the program. In the new version, a new diagnostic message V401 has been added, it lets find data structures which use memory uneconomically.

Constants processing has been improved, in a number of cases this reduces the quantity of false diagnostic warnings. The mechanism which hides double errors in header files indicated in relative views has been enhanced. Before that, during a project testing, the error in #include "lib\file.h" and #include "lib\..\lib\file.h" would be considered as if located in different files. Two diagnostic warnings would be given. Now paths are exposed, and the analyzer does not indicate twice the errors contained in the file "file.h".

Popular related articles


Comments (0)

Next comments next comments
close comment form