Hello Vicente, Am Saturday 28 February 2009 01:24:43 schrieb vicente.botet:
BTW, the doc html is not included
sorry - I'll add this soon
I was expecting that fro a long time. I was tried to do that, but the time goes on. Thanks a lot Oliver, I will take a deep look in.
I've also added two function in order to wait for multiple tasks (it uses Anthonies future lib wait_for_any()/wait_for_all() ).
So you don't need any more to provide get_future, isn't it?
Yes - the future should be an implementation detail for the task object. I believe the lib should provide a this_task::get_thread_pool() too (as you suggested). I've also some concerns about this_task::reschedule_until( function< bool() > const&) because the passed function object could block in bool operator()() (->for instance blocking in locking a mutex etc.). Maybe reschedule_until() should only accept futures?! Or schould I remove this function because pool::submit() called inside of a worker-thread would reschedule too. Oliver