Re: Multi-Threading Question
- From: Cool Guy <coolguy@xxxxxxx>
- Date: Sun, 11 Sep 2005 18:15:23 +0100
"Jon Skeet [C# MVP]" <skeet@xxxxxxxxx> wrote:
> That's certainly true. However, if the local variable is a reference to
> an object which is also being used and potentially changed on another
> thread, you need to use locks, volatile variables or explicit memory
> barriers to ensure safety.
In this case it's never being changed, although it is being used on another
thread.
Will the locking I'm already doing suffice here?
.
- Follow-Ups:
- Re: Multi-Threading Question
- From: Jon Skeet [C# MVP]
- Re: Multi-Threading Question
- References:
- Multi-Threading Question
- From: Cool Guy
- Re: Multi-Threading Question
- From: -
- Re: Multi-Threading Question
- From: Jon Skeet [C# MVP]
- Multi-Threading Question
- Prev by Date: Re: Multi-Threading Question
- Next by Date: Re: .NET SUCKS --- READ FOLLOWING. MICROSOFT IS A SUCKY CO
- Previous by thread: Re: Multi-Threading Question
- Next by thread: Re: Multi-Threading Question
- Index(es):
Relevant Pages
|