Re: Modifying outside properties from NSOperation subclass
Re: Modifying outside properties from NSOperation subclass
- Subject: Re: Modifying outside properties from NSOperation subclass
- From: Nick Zitzmann <email@hidden>
- Date: Mon, 14 Dec 2009 18:02:06 -0700
On Dec 14, 2009, at 5:54 PM, PCWiz wrote:
> Its being loaded into an NSOperationQueue, and I'm using methods like setObject:forKey: on the dictionary, not replacing the whole thing.
Then you need to lock and unlock everything that reads from or writes to the dictionary. Properties are no substitute for locking/unlocking the object, because atomic properties will protect the instance variable, but they won't protect the contents of the instance variable. @synchronized is the easy way of doing this, but depending on your needs, you might need NS(Recursive)Lock instead.
Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden