• 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
NSLock vs. NSRecursiveLock
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NSLock vs. NSRecursiveLock

  • Subject: NSLock vs. NSRecursiveLock
  • From: Tito Ciuro <email@hidden>
  • Date: Fri, 15 Oct 2004 10:19:50 +0200
Hello,

If I understand correctly, if a thread holds an NSLock and attempts to acquire it again, the thread will freeze. A solution is to use NSRecursiveLock instead, because the thread can acquire the lock multiple times without running into a deadlock.

So, is it safer to use NSRecursiveLock instead of NSLock? Are there instances where it's better to use NSLock over NSRecursiveLock? Are there any performance advantages perhaps?

Thanks,

-- Tito

_______________________________________________
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
  • Follow-Ups:
    • Re: NSLock vs. NSRecursiveLock
      • From: Wade Tregaskis <email@hidden>
  • Prev by Date: Re: Modal session requires modal window
  • Next by Date: Re: supplying default values to popup in table
  • Previous by thread: Re: AddressBook Woes
  • Next by thread: Re: NSLock vs. NSRecursiveLock
  • Index(es):
    • Date
    • Thread