]]
Sent: woensdag 1 mei 2002 07:13
To: [EMAIL PROTECTED]
Subject: [DOTNET] Threading Design Guidellines docs
I have been reading the docs on Threading Design Guidelines for Class
Library Developers and I ran across the following section I just don't
follow. Here is the first part of it:
Well, based on the text, I think there was a mistake...
>> Alternatively, it might be better to use more elaborate code to
>> create rhs outside of the lock, as in the following example. Then,
>> you can use an interlocked compare exchange to update x only if it
>> is still null. This assumes
I have been reading the docs on Threading Design Guidelines for Class
Library Developers and I ran across the following section I just don't
follow. Here is the first part of it:
Be aware of issues with the lock statement (SyncLock in Visual Basic).
It is tempting to use the lock statement t
