Given that Apple's Foundation does not support getting NSRunLoop from CFRunLoopRef, Cocotron designed CFRunLoop using toll-free bridging from NSRunLoop and GNUstep have a NSRunLoopFromCFRunLoop() (and GNUstep have some some NSRunLoop extensions allowing implementing this mess without fussing with CF.) function in their CoreFoundation implementation, is it safe to pass whatever object I got from the underlying framework over to the upper layer, with proper warning in the documentation?
Sent from my iPhone > On Nov 21, 2014, at 01:23, dangerwillrobinsondan...@gmail.com wrote: > > NSRunLoop can give you its underlying CFRunLoop > > The reverse is not possible. > CFRunLoop is not aware of NSRunLoop because NSRunLoop adds a thin > Cocoa/AppKit layer that CF doesn't have. (At least nothing in public API that > I can see ) > > Sent from my iPhone > >> On 2014/11/20, at 4:00, Maxthon Chan <m...@maxchan.info> wrote: >> >> The last three call back functions, beginning with _KLS, are the ones that >> will eventually call the delegate methods. However for delegate methods, >> didAdd and didRemove call for an NSRunLoop object that should map to the >> corresponding CFRunLoop passed into my call back. Any suggestions on how to >> do it? _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
