• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Is it always necessary to lock around mutations of an NSMutableDictionary?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is it always necessary to lock around mutations of an NSMutableDictionary?


  • Subject: Re: Is it always necessary to lock around mutations of an NSMutableDictionary?
  • From: Pontus Ilbring <email@hidden>
  • Date: Fri, 15 Jul 2005 14:02:54 +0200

On 7/15/05, Andrew Garber <email@hidden> wrote:
> In a multithreaded app, is it always necessary to lock around any
> changes you make to an NSMutableDictionary... even if you're only
> going to be adding new key-value pairs (i.e. never changing or
> removing the existing key-value pairs)?

Yes.

http://developer.apple.com/documentation/Cocoa/Conceptual/Multithreading/articles/CocoaSafety.html
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Is it always necessary to lock around mutations of an NSMutableDictionary? (From: Andrew Garber <email@hidden>)

  • Prev by Date: Re:Getting the download location selected by the user in Safari
  • Next by Date: Re: Is NSEntityDescription insertNewObjectForEntityForName:inManagedObjectContext: this slow?
  • Previous by thread: Is it always necessary to lock around mutations of an NSMutableDictionary?
  • Next by thread: More Sync Services Framework Questions...
  • Index(es):
    • Date
    • Thread