Dan Sugalski wrote: > [A] copying collector is generally untenable in a threaded environment.
Can you elaborate upon the reasoning behind this statement? > The first thing that any vtable function of a shared PMC must do is to > aquire the mutex of the PMCs in its parameter list, in ascending > address order. When the mutexes are released they are not required to > be released in any order. Note that this locking strategy cannot avoid deadlock if the user is allowed to acquire these locks--HLL locks must be altogether different beasts from automatic PMC locks. That's okay. Just a design consequence worth noting for everyone. -- Gordon Henriksen IT Manager ICLUBcentral Inc. [EMAIL PROTECTED]
