Disabling Warnings generated via CRT SECURE NO DEPRECATE

Question

What is the best way to disable the warnings generated via  CRT SECURE NO DEPRECATE that allows them to be reinstated with ease and will work across Visual Studio versions

User · Answer

i work on a multi platform project  so i can t use  s function and i don t want pollute my code with visual studio specific code  my solution is disable the warning 4996 on the visual studio project  go to Project -  Properties -  Configuration properties -  C C   -  Advanced -  Disable specific warning add the value 4996    if you use also the mfc and or atl library  not my case  define before include mfc  AFX SECURE NO DEPRECATE and before include atl  ATL SECURE NO DEPRECATE    i use this solution across visual studio 2003 and 2005   p s  if you use only visual studio the secure template overloads could be a good solution

User · Answer

You can define the  CRT SECURE NO WARNINGS symbol to suppress them and undefine it to reinstate them back

User · Answer

If you don t want to pollute your source code  after all this warning presents only with Microsoft compiler   add  CRT SECURE NO WARNINGS symbol to your project settings via  Project -  Properties -  Configuration properties -  C C   -  Preprocessor -  Preprocessor definitions    Also you can define it just before you include a header file which generates this warning  You should add something like this   ifdef  MSC VER  define  CRT SECURE NO WARNINGS  endif   And just a small remark  make sure you understand what this warning stands for  and maybe  if you don t intend to use other compilers than MSVC  consider using safer version of functions i e  strcpy s instead of strcpy

User · Answer

You could disable the warnings temporarily in places where they appear by using   pragma warning push   pragma warning disable  warning-code    4996 for  CRT SECURE NO WARNINGS equivalent    deprecated code here  pragma warning pop    so you don t disable all warnings  which can be harmful at times

User · Answer

The best way to do this is by a simple check and assess  I usually do something like this    ifndef  DEPRECATION DISABLE      One time only     define  DEPRECATION DISABLE      Disable deprecation true     if   MSC VER  gt   1400             Check version     pragma warning disable  4996     Disable deprecation     endif     if defined NMEA WIN   amp  amp    MSC VER  gt   1400      endif     ifndef  DEPRECATION DISABLE      All that is really required is the following     pragma warning disable  4996    Hasn t failed me yet  Hope this helps

User · Answer

For the warning by warning case  It s wise to restore it to default at some point  since you are doing it on a case by case basis    pragma warning disable  4996     Disable deprecation       Code that causes it goes here  pragma warning default  4996     Restore default

User · Answer

you can disable security check  go to  Project -  Properties -  Configuration properties -  C C   -  Code Generation -  Security Check  and select Disable Security Check   GS-

User · Answer

Combination of   macbirdie  and   Adrian Borchardt  answer  Which proves to be very useful in production environment  not messing up previously existing warning  especially during cross-platform compile    if   MSC VER  gt   1400             Check MSC version  pragma warning push   pragma warning disable  4996     Disable deprecation  endif                                        strcat base  cat                  Sample depreciated code                                        if   MSC VER  gt   1400             Check MSC version  pragma warning pop               Renable previous depreciations  endif

User · Answer

Another late answer    Here s how Microsoft uses it in their wchar h  Notice they also disable Warning C6386     inline  CRT INSECURE DEPRECATE MEMORY wmemcpy s  wchar t     CRTDECL wmemcpy  Out opt cap   N  wchar t   S1   In opt count   N  const wchar t   S2   In  size t  N         pragma warning  push        pragma warning  disable   4996 6386           return  wchar t   memcpy  S1   S2   N sizeof wchar t         pragma warning  pop

User · Answer

You can also use the Secure Template Overloads  they will help you replace the unsecure calls with secure ones anywhere it is possible to easily deduce buffer size  static arrays    Just add the following    define  CRT SECURE CPP OVERLOAD STANDARD NAMES 1    Then fix the remaining warnings by hand  by using the  s functions

[c++] Disabling Warnings generated via _CRT_SECURE_NO_DEPRECATE

Examples related to c++

Examples related to visual-studio

Examples related to visual-c++