_CRT_SECURE_NO_DEPRECATE would best be defined by bjam when TOOLS=vc-8_0, as many other Boost libraries get the same warnings. The deprecations are purely for security (potential buffer overflow) reasons. The help subsystem installed with the VC8 beta explains all. Lookup gets_s in the index, and then follow the link to "Security Enhancements in the CRT", to get up to speed quickly. - Keith MacDonald "Jonathan Turkanis" <technews@kangaroologic.com> wrote in message news:da472i$7d7$1@sea.gmane.org...
I think defining _CRT_SECURE_NO_DEPRECATE is something the end-user has to do, since by the time my headers are included the standard iostreams headers may already have been included.
Do you know any more details about the deprecation of these member functions? I was just guessing that the deprecation was for security reasons; can you confirm this? I'd also like to know what functions are supposed to replace them.
Thanks for your help!
Jonathan
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost