Re: userland supported APIs (was: Re: Synchronization primitives)
Re: userland supported APIs (was: Re: Synchronization primitives)
- Subject: Re: userland supported APIs (was: Re: Synchronization primitives)
- From: Terry Lambert <email@hidden>
- Date: Tue, 29 Apr 2008 12:14:42 -0700
On Apr 29, 2008, at 11:35 AM, Army Research Lab <email@hidden>
wrote:
Like I said before, no problem. I just want to have a definitive
answer
before I start relying on something that goes away.
Then you likely need to file a bug to obtain a definitive answer.
This is not an official support channel, and none of us speak for
Apple here, unless it's an announcement or a statement by DTS.
Some of us maintain some of the code we've been talking about, and may
have some influence on where it goes, but all we can really offer is
our own opinions.
So, to recap my understanding of all this:
1) It is possible to use stuff in /usr/include/libkern, but...
2) ...don't do that! It may/probably will go away at some point in
the
future as cleanup occurs.
Not what I said.
It's published. You are minimally going to be safe specifying a
deployment target, e.g. 10.5, and using it for a good long while. If
Dave and I have anything to say about it, it _will_ likely get moved
or renamed. We can't do anything unilaterally, we are small cogs on
larger teams, and there are other people whose opinions matter very
much, frequently more than ours.
3) There isn't anything quite like the OSAtomic* operators in user
space
that are truly supported (that is, won't be removed in the future
during
cleanup), and therefore if I want shared variables, I need to use
pthread_mutex_lock(), write my variable, and then unlock().
If it's currently documented, it's currently supported. Shawn already
pointed you at the documentation.
We don't really guarantee anything about future support, and I and the
rest of us (Dave Z., Shawn, etc.) are prohibited by our employment
contracts from making those kinds of statements. They are above our
pay grade.
If you need that kind of official statement, you need to file a bug to
get it (or an official "no comment").
Being from a military lab, you are undoubtedly familiar with "chain of
command". You are currently talking to S4s in a mess tent. 8-).
-- Terry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden