Erik Huelsmann wrote in a message to All:

 EH> What I was wondering is the following: When writing a dll that 
 EH> might be used for multiple threads, I want to have different 
 EH> variables (possibly with the same name, as they are passed in 
 EH> strings) for different threads. Is there a way to detect a 
 EH> thread has stopped and should disallocate the memory? 

Have the caller own a mutex semaphore which will, of course, be released
upon the owner dying.  Start a thread in the DLL for each such semaphore,
which will block until the owner releases it.  Then use the unblocked DLL
thread to do appropriate clean-up.
 
-- Mike


---