On Apr 21, 2011, at 4:18 PM, eveningnick eveningnick wrote: > I have an application that has a shared object (which is a custom > container for elements - arrays, and which is protected by critical > sections in my code). I need to control it's lifetime - it should be > alive until the last thread finishes working.
> Could you please suggest me how to achieve the removal of the object > when i need it? In the most "pretty" way, if one exists. How are you spawning your threads? If you use Cocoa methods, then they automatically retain the object which is the target of the selector and the argument object for the life of the thread. So, you may be getting this automatically without realizing it. If not, then it should be easy to arrange. If you're using some other technique to spawn your threads, you can just retain the object before spawning the thread and then have the thread work function or method release it before exiting. The retain and the release don't have to occur on the same thread. Regards, Ken _______________________________________________ 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
