VC STL - Visual Studio Beta 2 & INSECURE

Author

Visual Studio Beta 2 & INSECURE_DEPRECATE

Code4u

2005-08-16, 5:10 pm

We've just started to port our VS 2003 code to 2005. Off the bat I
noticed a 1001 deprecated function warnings. The library writer
appears to have marked every potentially buffer-overrunning library
function as deprecated with a variation of the INSECURE_DEPRECATE
macro. That's all well and good for Microsoft's security strategy, but
what about the rest of us that have used potentially harmful functions
such as sprintf? How can we selectively turn off these benign
warnings? Is this documented anywhere?

Doug Harrison [MVP]

2005-08-16, 10:03 pm

On Tue, 16 Aug 2005 14:43:34 -0700, Code4u <code4u@gmail.com> wrote:

>We've just started to port our VS 2003 code to 2005. Off the bat I
>noticed a 1001 deprecated function warnings. The library writer
>appears to have marked every potentially buffer-overrunning library
>function as deprecated with a variation of the INSECURE_DEPRECATE
>macro. That's all well and good for Microsoft's security strategy, but
>what about the rest of us that have used potentially harmful functions
>such as sprintf? How can we selectively turn off these benign
>warnings? Is this documented anywhere?

Look up the _CRT_SECURE_NO_DEPRECATE macro.

--
Doug Harrison
VC++ MVP

Sponsored Links