3 Jun
2008
3 Jun
'08
9:09 a.m.
Peter Dimov-5 wrote:
It can deadlock, but it cannot deadlock unexpectedly. That is, it will not turn code that didn't deadlock into code that deadlocks. Your example: -snip- already deadlocks without reuse.
You're right, I didn't see that. In a previous post you said "Limiting the reuse to pool threads eliminates most other (theoretical IMO) problems.". What theoretical problems has been identified with thread re-use? Does existing threadpools (such as java.util.concurrency.ExecutorService) offer thread re-use and if so is it considered an success? Johan -- View this message in context: http://www.nabble.com/-thread-pool-futures--Explicit-yielding-tp17606225p176... Sent from the Boost - Dev mailing list archive at Nabble.com.