RE: [INTERNALS-WIN] Re: VC15 or VS2017?

> -----Original Message-----
> From: Jan Ehrhardt [mailto:[email protected]]
> Sent: Wednesday, April 26, 2017 4:00 PM
> To: [email protected]
> Subject: Re: [INTERNALS-WIN] Re: VC15 or VS2017?
> 
> Hi Anatol,
> 
> Anatol Belski in php.internals.win (Wed, 26 Apr 2017 13:40:28 +0000):
> >When I look at paths like this
> >
> >C:\Program Files (x86)\Microsoft Visual
> >Studio\2017\Enterprise\VC\Redist\MSVC\14.10.25008\x64\Microsoft.VC150.C
> >RT
> >
> >so it appears it still calls CRT vc15. It might be mistake or not, vcXX
> >is what we use for the shortcuts and the name is what one sees
> >explicitly here. 14.10 is the toolset version, 1910 is compiler
> >version, etc. We always refer to the runtime version.
> 
> Wow, you have to dive really deep to find a reference to VC15(0). Inside that dir
> there are *140.dll's with a file version 14.10.25008.0.
> 
> I can imagine you do not want to change the terminology, but Microsoft does
> not make it easy by introducing a toolset that does not match the CRT.
> --
Yeah, probably no one can be really hapyy with this. And it might be indeed a mistake as stated at a couple of other places besides those you've linked. Anyway, this time it's something even more unusual even for those used to it 😊 There were obviously no other way to introduce the binary compatibility, other than keeping the dll names same. While it's functionally correct, I guess it will be a cause of confusions for users, where they fe get newer PHP binaries, but don't install the upgraded runtime. In that case, the older CRT might still be found and behave a wrong way. Heh.

Regards

Anatol