Gary,

My simple-minded view of this is that anything with Shared or Weak in
the name must be thread-safe.  The weak collections are manipulated by
at least two threads, the caller and the weakling cleanup thread.

Thanks for stress testing this!

Bill





Gary Chambers <gazzaguru2 at ...> wrote:
If you can think of a better way of blocking if finalization is in
progress...
only WeakRegistry has its own protection semaphore at present. (uses
WeakKeyDictionary, rather than Identity, oddly).


Wilhelm K. Schwab, Ph.D.
University of Florida
Department of Anesthesiology
PO Box 100254
Gainesville, FL 32610-0254

Email: bschwab at anest.ufl.edu
Tel: (352) 846-1285
FAX: (352) 392-7029