On 10 Apr, 2014, at 6:20 pm, Dave <d...@looktowindward.com> wrote: > Hi, > > I was confused by this: > >> It also doesn't make sense to synchronize on the myDict object. That's what >> is in flux. You should synchronize on "self", the object which owns and >> manages myDict. > > Surely as long as every access to the dictionary is @synchronized to the same > entity it’s fine? > > The way I’d atcheive this is to make the NSMutableDictionary a private > property: > > @property (nonatomic,strong) NSMutableDictionary* pDictX; > > and define public methods: > > -(void) removeObjectFromDictXWithKey:(NSString*) theKey; > -(void) addObject:(id) theObject toDictXWithKey:(NSString*) theKey; > -(id) getObectFromDictXWithKey:(NSString*) theKey;
Yes but that's not what he's doing, he's not mutating the dictionary (even though it's mutable), he's replacing one dictionary with another one. So the point of synchronizing on self in that case is to prevent the dictionary being swapped out between calls. > >>> >>>> On Mar 31, 2014, at 10:16 PM, Trygve Inda <cocoa...@xericdesign.com> wrote: >>>> >>>>> I need to be able to set a new myDict and not have it happen between the >>>>> reading of different values from the dictionary by other threads. >>>> _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
