On 20 March 2017 at 22:17, Stephan T. Lavavej
[Mateusz Loskot]
I don't think this is argument holds strong in practice. AFAIK, PlatformToolseVersion and its derivatives used in Boost are never compared as range, like _MSC_VER often is, but as exact values. Boost tests for: v140 v141 and, if at any time Microsoft replaces it with, STL (tm): meow let it be so.
FYI, we're planning to release a toolset that will be binary-incompatible with v140 and v141 at some point in the future (the libraries, and probably the compiler too, will be bin-incompatible, to allow us to make significant improvements to data structure layout and so forth that we're otherwise unable to make).
Thanks Stephan, I always appreciate all the updates and clarifications you give.
We haven't decided on that toolset's versioning at this point. (I expect/hope that it will be very distinctive and not easily confused with the current versions; Visual C++ vMeow does have a nice ring to it...)
+1 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net