On Tue, Jul 02, 2013 at 12:38:29PM +0200, Mathias Gaunard wrote:
On 02/07/13 01:35, Lars Viklund wrote:
Boost.Signals VS2013 Preview version bump https://svn.boost.org/trac/boost/ticket/8755 The BOOST_WORKAROUND macros at boost/signals/detail/named_slot_map.hpp:130 and libs/signals/src/named_slot_map.cpp:27 needs to be increased to <= 1800 in order to encompass the Visual Studio 2013 Preview compiler.
Boost.MPL VS2013 Preview version bump https://svn.boost.org/trac/boost/ticket/8756 The BOOST_WORKAROUND macros at boost/mpl/assert.hpp lines 37 and 247 need to be changed to also consider BOOST_MSVC, == 1800, patch attached.
I'm not sure fixing these right now is a good idea, since it's just a preview version. The final version will also be 1800, and it might behave differently.
How about a workaround using the _MSC_FULL_VER of this release then where suitable? Note that this isn't like the previous CTPs, it has the go-live blessing from the vendor that allows its use in production. In my eyes there's two paths here: a) do nothing, and both the Preview and the RTM will be broken until at least the Boost version shipping after RTM is available; b) implement sufficient fixes for Boost to work with the Preview, allowing people to find and report issues, and when RTM ships, have a chance of at least some support in a released Boost version. Is it really worth some effort saving now to have a multi-month period at RTM launch where the compiler is utterly unusable? This is after all one of the top-tier toolchains that Boost aims to support. -- Lars Viklund | zao@acc.umu.se