[Boost-users] Problem with 'future' on compiler without move semantics

In my earlier note, I figured it should just work. But it's not. I think it might be different on Boost 1.47? Can anyone give me a VERY QUICK answer on how to return a unique_future on a compiler without && using Boost 1.47? Thanks! —John In file included from /Volumes/VSee_Source/svnTree/Trunk/stable/Testing/UnitTests/Tools/threadpoolTest.cpp:2: ⋯: error: calling a private constructor of class 'boost::unique_future<int>' return future_result; // built-in mover via implicit conversions ^ /⋯lTest.cpp:61:30: note: in instantiation of function template specialization 'vst::async' requested here vst::unique_future<int> fi= vst::async (&calculate_the_answer_to_life_the_universe_and_everything); ^ /opt/local/include/boost/thread/future.hpp:619:9: note: implicitly declared private here unique_future(unique_future & rhs);// = delete; ^