New SDKs & transition to C++11
Posted: Fri Nov 11, 2016 3:44 pm
As far as I understand the new SDKs will finally enable us using C++11, so considering that these new SDKs are almost ready I assume this switch is imminent. As MSVC 2013 and the v120 toolset apparently have only rudimentary C++11 support, I guess that also means that support for MSVC 2013 will be deprecated? I'm asking because I want to know if I should/have to upgrade the dev environments on my Win machines to MSVC 2015.
The second thing is the naming scheme for the new SDKs. @Marcel, I've seen that you introduced a version numbering scheme based on the FO version. I'm wondering if that really makes much sense, as the version of the SDK isn't really tied to that of FO itself - if anything, it's tied to a specific point in the commit history, usually because you need a certain version of the SDK to be able to build FO from a certain commit onward, and/or the other way round: a certain version of the SDK can only be used to build FO from a certain commit onward.
Which is why we used to base the SDK version only on the date.
I actually don't have a strong objection against your new scheme, I just don't see the point. If Geoff also thinks it's okay, I'm fine with that - Geoff?
The second thing is the naming scheme for the new SDKs. @Marcel, I've seen that you introduced a version numbering scheme based on the FO version. I'm wondering if that really makes much sense, as the version of the SDK isn't really tied to that of FO itself - if anything, it's tied to a specific point in the commit history, usually because you need a certain version of the SDK to be able to build FO from a certain commit onward, and/or the other way round: a certain version of the SDK can only be used to build FO from a certain commit onward.
Which is why we used to base the SDK version only on the date.
I actually don't have a strong objection against your new scheme, I just don't see the point. If Geoff also thinks it's okay, I'm fine with that - Geoff?