1 Dec
2012
1 Dec
'12
12:36 p.m.
On 1 December 2012 05:34, Eric Niebler <eric@boostpro.com> wrote:
On other words, we should operate under the assumption that there will be no improvements in C++11 compliance of any officially supported Microsoft compiler until the next major release of Visual Studio.
[snip]
What that means for Boost is up for us to decide. But given the above, I think it would be wise for us to add support for the CTP releases to Boost.Config using _MSC_FULL_VER so that we don't have to wait until VS.Next to start taking advantage of variadic templates (for example).
Maybe we should make support of CTP features optional, i.e. we only use the feature if the user sets a macro. That way, the default build won't break if a feature is removed.