Re: Order of resulting selector invocations from performSelector
Re: Order of resulting selector invocations from performSelector
- Subject: Re: Order of resulting selector invocations from performSelector
- From: glenn andreas <email@hidden>
- Date: Fri, 14 Mar 2008 09:15:49 -0500
On Mar 14, 2008, at 3:52 AM, Stuart Malin wrote:
If I have my code issue multiple
performSelectorOnMainThread:someSelector :waitUntilDone:NO
is there any guarantee about the resulting order of execution?
(please note that I passed in NO for waitUntilDone)
If there's nothing in the documentation about this, the answer is no,
there is no guarantee.
That is, if for the same object, if performSelectoronMainThread is
executed twice, first for selectorA, and then for selectorB, can I
reasonably expect that selectorA will be invoked before selectorB ?
It may seem reasonable, but without definite documentation on that, I
wouldn't depend on that. Seems like a good place for bugs to sneak in
that are nearly impossible to diagnose...
Glenn Andreas email@hidden
<http://www.gandreas.com/> wicked fun!
Cardographer | the custom playing card designer
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden