Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I just recently changed my IDE to MS Visual Studio 2005 coming from MSVC++ 6, and I’ve gotten a lot of deprecation warnings. Rather than ignore the warning, I started to change them to the _s equivalents. However, I then found out that these were microsoft-only implementations.
I read somewhere that they were pushing for these to become part of the standard. Is it?
Is it a good idea to use these _s functions? Or should I use something else?
Thanks.
The
*_s()functions are not part of the C standard, but there is a pending ‘Technical Report’ proposing that they be added (I’m not sure if the routines in the TR are exactly the same as Microsoft’s or if they’re just similar).TR 24731-1: Extensions to the C Library Part I: Bounds-checking interfaces:
If you want to continue to use the old functions you can keep the deprecation warnings quiet by defining the macro
_CRT_SECURE_NO_WARNINGS(was_CRT_SECURE_NO_DEPRECATEwhich might still be supported).