Re: [boost] [boost.build] should we not define _SECURE_SCL=0 by default for all msvc toolsets

Subject: Re: [boost] [boost.build] should we not define _SECURE_SCL=0 by default for all msvc toolsets
From: OvermindDL1 (overminddl1_at_[hidden])
Date: 2008-12-21 17:38:03

On Sun, Dec 21, 2008 at 2:06 PM, Anteru
<newsgroups_at_[hidden]> wrote:
> OvermindDL1 schrieb:
>> Do you have a link to send me to for that?  I buy VS by itself, I do
>> not have an MSDN subscription (I do not even make that much spare
>> money a year), as such I do not often stay with the 'in' Microsoft
>> community, end up figuring most out by myself.  I actually compile
>> more for *nix, but all by coding takes place in Visual C++ and Visual
>> Assist until there is a 'nix IDE that is mostly-comparable.  Just this
>> issue was odd in that GCC *vastly* outperformed VS, when usually VS is
>> usually a 'little' bit faster then GCC in compiled code, had to look
>> in to it.
>
> I guess stl_at_[hidden] should do the job. That should be their STL
> developer (Stephan T. Lavavej).

Ah, thanks.  I have a wonderful example to send that shows how without
the above commands completely destroys many optimization
opportunities...

So, to poke everyone again.  Is it planned to add the above line as
another build configuration?