[cpp-threads] Asynchronous Function Proposal
Lawrence Crowl
Lawrence at Crowl.org
Sat Jun 13 05:02:25 BST 2009
On 6/4/09, Doug Lea <dl at cs.oswego.edu> wrote:
> However, you can do a little better than always creating a thread
> by using a caching thread pool. As in the one java supplies in
> java.util.concurrent.Executors.newCachedThreadPool. This reuses
> a thread if one previously created is available, else creates
> one. Ours also bounds the keep-alive interval to kill off those
> that have not been used for a while.
Because C++ potentially operates in an environment with dynamic
loading and unloading of libraries, it is a little more important
to know when thread_local variables have been destroyed, so that one
does not unload their destructors before destroying the corresponding
variables.
--
Lawrence Crowl
More information about the cpp-threads
mailing list