Re: [boost] [build] VC++ 2017 version number?

Subject: Re: [boost] [build] VC++ 2017 version number?
From: Olaf van der Spek (ml_at_[hidden])
Date: 2017-03-14 08:27:24

On Mon, Mar 13, 2017 at 10:58 PM, Stephan T. Lavavej via Boost
<boost_at_[hidden]> wrote:
>> As I said before, for my opinion, I think we should move to msvc-15.0 for the toolset, as that will be *less* confusion for the end-users.
>
> I disagree - 15 is the IDE's version number. The IDE can host multiple toolsets (already it can install v140 and v141; expect more in the future).

In the past IDE and toolset version numbers were equal weren't they?

> Another approach would be to give up on the 14.x version numbers entirely (admittedly it is confusing to have the v141 toolset linking against msvcp140.dll for bincompat). Instead, use _MSC_VER as the toolset identifier - this is 1900 for VS 2015 (RTM/Updates) and 1910 for VS 2017 RTM, and will increase in a fairly predictable, monotonic way in the future.

Can't MS use a single version number for the compiler *and* the toolset?

-- 
Olaf