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.

>
>
>
V2002. Consider using the 'Ptr' version…
menu mobile close menu
Analyzer diagnostics
General Analysis (C++)
General Analysis (C#)
General Analysis (Java)
Micro-Optimizations (C++)
Diagnosis of 64-bit errors (Viva64, C++)
Customer specific requests (C++)
MISRA errors
AUTOSAR errors
OWASP errors (C#)
Problems related to code analyzer
Additional information
toggle menu Contents

V2002. Consider using the 'Ptr' version of the 'foo' function here.

Dec 15 2011

This diagnostic rule was added at users' request.

The analyzer allows you to detect calls of functions that have 'Ptr' analogues. By this term we mean functions whose name has the Ptr suffix. Some of these extended functions are: SetClassLongPtr, DSA_GetItemPtr.

Consider the following source code:

void foo(int a);
void fooPtr(int a, bool b);
void foo2();
...
void test()
{
  foo(1); // V2002
  foo2(); // OK
}

In the fragment where the "foo" function is called, the V2002 diagnostic message will be produced since there is another function with the same name but ending with "Ptr". The "foo2" function does not have an alternative version and therefore no diagnostic message will be generated concerning it.

The V2002 message will be also generated in the following case:

void fooA(char *p);
void fooPtrA(char *p, int x);
...
void test()
{
  fooA(str); // V2002
}

V2001 is a related diagnostic message.

This diagnostic is classified as: