Re: CFRunLoopStop too powerful when invoked by bootstrap per-user daemon?

Subject: Re: CFRunLoopStop too powerful when invoked by bootstrap per-user daemon?

From: Dave Zarzycki <email@hidden>

Date: Fri, 2 Nov 2007 10:07:33 -0700

Delivered-to: email@hidden

On Nov 2, 2007, at 9:39 AM, Pete Gontier wrote:

CFRunLoopStop is documented as stopping the “innermost activation” of the given run loop. In a regular application (a Cocoa app which calls NSApplicationMain), this seems to be the case. However, in a bootstrap per-user daemon (which calls CFRunLoopRun and CFRunLoopRunInMode), CFRunLoopStop seems to stop all activations of the run loop. Or perhaps I should say both, since we have only two. This happens under both Tiger and Leopard. Has anybody else encountered this? Is there a downside to simply invoking the outer run loop again if/when it exits before we wanted?

FYI –

Despite being in Darwin, CoreFoundation is still actively maintained by the Mac OS X side of the company. You'll have much better luck getting your CF questions answered on a more Mac OS X specific (i.e. not Darwin) mailing list.

davez

_______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/email@hidden This email sent to email@hidden

References:
	>CFRunLoopStop too powerful when invoked by bootstrap per-user daemon? (From: Pete Gontier <email@hidden>)