If you can target Leopard and above, @synchronized is probably a better route to go though as scott said, the object to be synchronized around would need to be checked by all methods using it (in your case this would be the instance of the NSLock).

-rob.

On Dec 22, 2008, at 10:12 AM, Scott Ribe wrote:

The lock (the same one) has to be used by all the methods to coordinate access. Taking a lock in updateDirectoriesInThread doesn't magically make
addDirectory and removeDirectory wait for the lock.

--
Scott Ribe
scott_r...@killerbytes.com
http://www.killerbytes.com/
(303) 722-0567 voice


_______________________________________________

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:
http://lists.apple.com/mailman/options/cocoa-dev/rob%40pinchmedia.com

This email sent to r...@pinchmedia.com

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________

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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to