"George M. Garner Jr." <gmgarner@erols.com> writes:

Beman,

I tried adding the following to the end of visualc.hpp and then recompiled the serialization and regex libraries without problem:

//http://msdn.microsoft.com/visualc/default.aspx?pull=/library/en-us/dnvs05/ht... #if (_MSC_VER >= 1400) // 1400 == VC++ 8.0 # define BOOST_HAS_NRVO #endif

At least there is no harm in defining it.

It could be slowing things down. -- Dave Abrahams Boost Consulting www.boost-consulting.com

...

Config info isn't reporting BOOST_HAS_NRVO as being set.

Is config broken, or is MS wrong?

Is config info just a report? I thought it was automatically generated.

Yes config_info is just a report, config_test is the consolidated test program for Boost.Config. Turning BOOST_HAS_NVRO on for VC8 causes the test program to fail, unless optimisations are turned on, in which case it is indeed supported. So I suggest we add: #if (_MSC_VER >= 1400) && !defined(_DEBUG) # define BOOST_HAS_NRVO #endif to visualc.hpp, note that _DEBUG isn't really the right macro to use here, but it's as close an approximation as we can get. Thoughts? John.

...

Turning BOOST_HAS_NVRO on for VC8 causes the test program to fail, unless optimisations are turned on, in which case it is indeed supported.

Should that be a warning instead of fail? It's an optimisation missing, not a "broken" config that leads to errors.

Um, if it was a warning then the configure script would turn on BOOST_HAS_NVRO for *everything* which isn't really what we want, I could hack the test so it's a warning for VC8 only I guess. John.