"William E. Kempf" <[EMAIL PROTECTED]> writes: > Actually, there's another minor issue as well. The user can call > operator() and then let the async_call go out of scope with out ever > calling result(). Mayhem would ensue. The two options for dealing > with this are to either block in the destructor until the call has > completed or to simply document this as undefined behavior.
If you want async_call to be copyable you'd need to have a handle-body idiom anyway, and something associated with the thread could be used to keep the body alive. -- Dave Abrahams Boost Consulting www.boost-consulting.com _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
