Thorsten Schuett wrote:
In another reply, thread-cancellation was mentioned. We don't have thread-cancellation currently, but it would be nice if future<> would not only accept functors but also allow for an optional interface to be passed for signaling an abort request. A user would then be able to implement a mechanism that works form her/him. Maybe, an abort policy would be the right thing here.
This depends on the cancelation possibilities in boost.thread.
No, it doesn't. The whole point is that the user is enabled to implement his own abort-signaling mechanism (e.g. by setting a flag that gets read by the running thread, or by writing to an additional file descriptor used in a call to select() in the code run by the thread). Regards, m Send instant messages to your online friends http://au.messenger.yahoo.com