Re: [boost] Let's stop distributing binaries

Subject: Re: [boost] Let's stop distributing binaries
From: Robert (r.firl_at_[hidden])
Date: 2018-08-31 13:43:06

On 8/31/2018 1:10 AM, Olaf van der Spek via Boost wrote:
> On Thu, Aug 30, 2018 at 11:49 PM, Robert via Boost
> <boost_at_[hidden]> wrote:
>> compiled as expected.  Plus, soon the default will be C++17. Expect the VS
>> 15.9.x release to have that value, assuming past language compliance
>> modifications, indicate future unexpected compiler messages, warnings,
>> errors, etc.
> 
> Source?
Daily professional use of the current release VS tool set.

Details:
Microsoft anticipates the 15.9.x release(s) will resolve bugs complying 
with C++17.  Plus, the standard headers will likely change again. 
Between 15.7.x and 15.8.x, the VS standard headers use more compile time 
if and other C++17 features.  The header modifications are quickly found 
using the Intel 18.0, update 3, C++ compiler. The Intel C++ compiler 
team has been informed and issues filed.  How exactly will the changing 
VS standard header files compile without C++17 being the 15.9.x default?

Additional Reference:
https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/

Remember, the VS preprocessor is expected to be fully compliant too:
The updated preprocessor is currently under the switch 
/experimental:preprocessor until it is fully implemented and 
production-ready, at which point it will be moved to a /Zc: switch which 
is enabled by default under /permissive- mode.

From:
https://blogs.msdn.microsoft.com/vcblog/2018/07/06/msvc-preprocessor-progress-towards-conformance/

--Robert

> 
>