{"id":114,"date":"2006-02-24T11:38:41","date_gmt":"2006-02-24T16:38:41","guid":{"rendered":"http:\/\/bitpost.com\/news\/2006\/02\/24\/visual-studio-2005-and-boost-compatibility\/"},"modified":"2006-04-07T10:10:54","modified_gmt":"2006-04-07T15:10:54","slug":"visual-studio-2005-and-boost-compatibility","status":"publish","type":"post","link":"https:\/\/bitpost.com\/news\/2006\/visual-studio-2005-and-boost-compatibility\/","title":{"rendered":"Visual Studio 2005 and boost compatibility"},"content":{"rendered":"

I was hoping to start using Visual Studio 2005 as my primary Windows compiler, but this warning from the boost home page<\/a> was holding me back:<\/p>\n

Note: Boost does not support the non-standard “Safe” C++ Library shipping with Visual C++ 8.0, which may result in many spurious warnings from Boost headers and other standards-conforming C++ code. To suppress these warnings, define the macro _SCL_SECURE_NO_DEPRECATE<\/code>.<\/p><\/blockquote>\n

Digging further on boost.org…<\/p>\n

The implementation of the standard C++ library bundled with Visual C++ .NET 2005 might issue a number of spurious warnings feature is deprecated<\/em> when using Boost headers. The warnings come from the “Safe” C++ Library, which labels many standard C and C++ library constructs as deprecated when in fact they may be used safely and correctly. Define _SCL_SECURE_NO_DEPRECATE<\/code> globally to eliminate these errors. Alternatively, you can enclose all includes of Boost headers and C++ standard library headers with #pragma warning(disable:4996)<\/code>, as demonstrated below:<\/p><\/blockquote>\n

\n
\n
#pragma warning(push)\r\n#pragma warning(disable : 4996)<\/pre>\n
#include\r\n#include\r\n#include\r\n#include\r\n#include<\/pre>\n
#pragma warning(pop)<\/pre>\n<\/blockquote>\n<\/blockquote>\n
So it sounds like Microsoft is basically saying “don’t use these standard C++ features as we’ve found them to be unsafe”.  Fair enough, and it seems fairly harmless if  you can easily disable the warnings.  I’ve heard that Microsoft has a whole range of features that are illegal for including in any newly submitted code, e.g. all the crappy C string routines – MAN how much pain have THEY caused over their lifetimes.  Wow, I just agreed with Microsoft.<\/p>\n","protected":false},"excerpt":{"rendered":"
I was hoping to start using Visual Studio 2005 as my primary Windows compiler, but this warning from the boost home page was holding me back: Note: Boost does not support the non-standard “Safe” C++ Library shipping with Visual C++ 8.0, which may result in many spurious warnings from Boost headers and other standards-conforming C++ […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[10,2],"tags":[],"class_list":["post-114","post","type-post","status-publish","format-standard","hentry","category-tricks-tips-tools","category-chatter"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t