VC15 or VS2017?

[email protected] (Jan Ehrhardt) Wed, 26 Apr 2017 03:53:22 +0200
Newsgroups php.internals.win
Message-ID <[email protected]>
Quoting https://www.apachelounge.com/viewtopic.php?p=35260#35260

>Up until now the toolsets were closely tied to the VC version.
>VS 2008 - VC9 -> v90, VS 2012 - VC11 -> v110, VS 2015 - VC14 -> v140,
>but VS 2017 - VC15 brings only v141. This reflects the binary
>compatibility of builds by VC14 and VC15, but the numbering system is
>more confusing then ever before.

Wouldn't it be that Microsoft gradually drops the VC-numbering? We are
calling Visual Studio 2017 VC15, but what is the ground for that?

Even the redistributables do not call themselves VC15. See
https://www.visualstudio.com/downloads/
Bottom > Open 'Other Tools and Frameworks' > Lowest download.

When installing the VS 2017 redistributable, it announces it self as
'Microsoft Visual C++ 2017 Redistributable (x64) - 14.10.25017'.

Should we drop 'VC15' in favour of 'VS2017'?
-- 
Jan