On Oct 5, 2008, at 4:43 PM, Brian Stern wrote:
This is the question I really wanted to ask:
I have an object X that is alloc/inited on the main thread. This
object creates some NSThreads with
detachNewThreadSelector:toTarget:withObject, which have object X as
their target. At a later point I want to release object X and have
it be dealloced on the main thread.
How do I guarantee that object X is dealloced on the main thread?
The problem is this: the NSThread objects retain object X. I have a
stop method in object X that sets a 'cancelled' global that the
thread objects inspect and they then exit when it turns true. So I
send stop and then release on the main thread. The thread objects
exit and eventually release object X but the last release, which
causes the dealloc, can be on any thread.
The real question is, why do you care what thread the -dealloc method
runs on?
What non-memory management side effects does your -dealloc method have
which much be run on the main thread?
Jim
_______________________________________________
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 [EMAIL PROTECTED]
