🚀 go-pugleaf

On Thu, 29 May 2003 14:39:14 +0200, "Tharun Pillay" <tharun@webmail.co.za>
wrote:

>My worker thread is responsible for pooling, queues, etc. and my
>deallocation thread frees memory when the threads in the pool have
>terminated (it does this by checking GetExitCodeThread). I've managed to
>solve it by setting a flag for when the deallocation thread can free, though
>this seems a bit prone to disaster. Especially since the worker threads
>objects are derived from a base class and setting the flag is the classes
>responsibility.

I would take a look at some code that manages a thread pool
'cause it can be kind of tricky.  Generally memory should be
freed by the same thread that allocates it(unless it's some
heap allocation that has a thread id in the call to deallocate
etc. or you are destroying objects created in the manager
thread or something else that makes sense.)

I think it is best to get some separation or "loose coupling"
between the thread you are going to kill/free and the pool
manager.  So some type of Kernel Object is probably a
good idea.  You might take a look at some of the C++
programming sites for thread pool algorithms or patterns.
Try MSDN and http://www.windevnet.com/

Also if you know Delphi you might see something good
on Torry's site.  I use a Delphi Component TMultiTasker
for multi-thread stuff in Delphi.  Looking at the source
might be helpful esp. if you use VCL thread objects.

-- 

"I don't want to belong to any club that would have me as a member."

    -- Groucho Marx