11 Mar
2007
11 Mar
'07
4:45 p.m.
Here is another question/comment as I move through this implementation: I see a strong need for future<void>. If I build my multi-threaded task scheduling system around future, I will likely have some invocations which do not return a value, but which I do want to synchronize with, receive exceptions from, and possibly cancel(). Has there been any work/thoughts how to handle this? Should future<void> be allowed? Thanks for the other info Peter and your implementation - very useful. Braddock Gaskill Dockside Vision Inc