|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
> -----Original Message----- > From: Kevin Van Vechten [mailto:email@hidden] > Sent: Friday, November 18, 2005 9:26 PM > To: Philip Lukidis > Cc: email@hidden > Subject: Re: custom runloop notification- which approach to take? > > > > On Nov 18, 2005, at 11:55 AM, Philip Lukidis wrote: > > > Thanks for your reply. I guess then I'll use CFMessagePort, since I > > would not have to use mach API calls. > > Yes, CFMessagePort is the preferred API. > > > Not to complain, but is there any official documentation > for the mach > > API anywhere? Not including header files or source. Or is this > > Apple's > > way of discouraging people from using it? > > I think you've correctly identified the situation. Mach is > considered private interface, and there have never been any > guarantees about its compatibility from release to release. > > - Kevin > OK, thanks for confirming my suspicions. It's fine for me, CFMesagePort does what I need. Philip Lukidis _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-userlevel mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.