Subj : Re: [.NET] Lock Object
To   : comp.programming.threads
From : Cool Guy
Date : Sat Sep 24 2005 03:02 pm

Joe Seigh <jseigh_01@xemaps.com> wrote:

>> Consider that several threads, which may run Test.A() and/or Test.B(), may
>> already be running before /fooLock/ gets assigned.
> 
> It should be taken care of by object initialization.

Actually I should've mentioned that I had a Singleton with lazy
instantiation in mind when I wrote that.

Thanks

.