site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On May 5, 2006, at 8:46 AM, Philip Lukidis wrote: Yep. -invalidating the timer (via CFRunLoopTimerInvalidate()) -removing the timer (via CFRunLoopRemoveTimer()) Yes, this will stop the run loop (even if it still has valid sources). For sources that are of type CFRunLoopSourceRef, yes. - Kevin _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... Hello. I hope that I'm posting this to the correct list. Concerning CF, I was wondering if the following scenario is correct: A "parent" thread creates a child thread via the pthread library. The child thread has only 1 runloop source on it (a timer in fact), and once the timer is applied onto the child runloop by the child itself, the child proceeds to call CFRunLoopRun() on itself. Now the parent is responsible for running down this child on demand. Can the parent rundown the child by: I'm not sure what you mean by "rundown," but I'll assume you mean stop the child's runloop. It's my understanding that a RunLoop will stop running when it has no more valid sources or timers to listen to. So if there is only one timer in the run loop, either of these would accomplish your goal. -calling CFRunLoopIsWaiting() in a while loop until it returns true (which indicates that all callbacks have drained and that it is waiting again, but of course since the timer was invalidated it can never be called again). Of course I should NOT holding a resource which the callback might need in order to execute and exit. While I'm sure you could make something like this work, it's pretty contrived. -calling CFRunLoopStop() -calling pthread_join() on the pthread I don't think this will stop the run loop. Instead, it will block the parent thread until the child thread exits. Can this also be extended to other runloop sources, by using CFRunLoopSourceInvalidate() instead of CFRunLoopTimerInvalidate(), and CFRunLoopRemoveSource() instead of CFRunLoopRemoveTimer()? If these procedures are incorrect, why so, and what are the alternatives? I don't see any of the above as "alternatives." In your case, with only one runloop source, CFRunLoopTimerInvalidate(), CFRunLoopRemoveTimer(), and CFRunLoopStop() all have the same end- result. However, this is a consequence of a simple example, and not generally true. Invalidating and removing a source have different semantics. For example, you may want to invalidate a source (no matter how many runloops may be using it), or alternatively you may want to remove a source from a particular runloop but keep it as a source in another runloop (or perhaps add it back to the same runloop at a later time). Stopping a runloop doesn't affect any of the sources, so it can be restarted at a later time in the same configuration that it was in originally. This email sent to site_archiver@lists.apple.com