Niels Dekker - address until 2010-10-10 wrote:
Robert Stewart wrote:
I can see that being an issue if the tests are compiled with C++0x features enabled. Otherwise, MSVC 10 is wrong.
I'm not sure, but it looks like MSVC 10 will always have its C++0x features enabled. The <bitset> header of MSVC 10 beta 1 only offers the old C++98/03 bitset(unsigned long) constructor if the macro _HAS_CPP0X is /not/ defined. But apparently _HAS_CPP0X /is/ defined, at least on the msvc-10.0 RC configuration tested here by Juergen Hunold, and on the regression site, www.boost.org/development/tests/trunk/RWVC10.html I tried to un-define _HAS_CPP0X (compiler option "/u _HAS_CPP0X"), but it doesn't seem to work.
There is some logic in yvals.h which defines _HAS_CPP0X to 1 if it's not defined already (and by default, it is defined and set to 1). If you manually define _HAS_CPP0X=0 in the project options, then the C++0x features will be disabled. -- View this message in context: http://old.nabble.com/-utility-swap--MSVC-10-test-failure%2C-unsigned-long-t... Sent from the Boost - Dev mailing list archive at Nabble.com.