Re: [Boost-users] [boost] [boost.build] should we not define_SECURE_SCL=0 by default for all msvc toolsets

Subject: Re: [Boost-users] [boost] [boost.build] should we not define_SECURE_SCL=0 by default for all msvc toolsets
From: Jean-Francois Bastien (jfbastien_at_[hidden])
Date: 2008-12-04 16:34:51

>> But AFAIK, even the prebuilt binaries that you get from Boost 
>> Consulting are built with _SECURE_SCL=0.
> 
> Really ???  I hadn't realised that, that's not good IMO, given
> that the define changes the ABI away from the compilers default.

> One thing I hope we can all agree on: this should be a toolset
> feature, and it should change the library-name-mangling so
> that auto_link.hpp can select the correct binary (it doesn't
> at present, but just let me know what the correct name-mangling
> is and I'll fix that).

There have been a few discussions in the past on this, see this little
research and proposal I did a few weeks ago:
http://www.nabble.com/MSVC-_SECURE_SCL-causes-ABI-change%2C-ODR-violatio
n---mangle-library-names--td19919013.html#a19919013

JF