Re: Latest Documentation?
Re: Latest Documentation?
- Subject: Re: Latest Documentation?
- From: John Lazzaro <email@hidden>
- Date: Thu, 14 Feb 2002 16:38:09 -0800
>
Darren Gibbs <email@hidden> writes:
>
>
With all this talk of documentation, I'm curious if people can
>
articulate exactly what's missing that they _need_.
The audio API is only half the story -- pro applications need
real-time scheduling and memory locking APIs that are up to
the task and well documented.
All I want is for Darwin to match Linux in this regard -- in
Linux:
man sched_setscheduler
man mlock
is a good start, these FAQs:
http://www.linuxdj.com/audio/lad/resources.php3
tell how audio programmers should use these Linux scheduling
and memory APIs in real applications, and for those who need
more background material, the O'Reilly book referenced in
the sched_setscheduler man page tells the complete story of
the POSIX real-time APIs and how to use them.
To my knowledge, the best we have right now in Darwin is a
set of random emails buried deep in coreaudio-api, showing
the syntax of Mach calls. APIs like these need more -- they
need the contract the programmer and the OS make to be
extremely explicit, so that everyone knows what is to be
relied upon and what changes from OS revision to OS revision.
These tools aren't nice-to-haves -- they are essential for
sophisticated, multi-thread apps to work as professionals
want them to work.
-------------------------------------------------------------------------
John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
lazzaro [at] cs [dot] berkeley [dot] edu www.cs.berkeley.edu/~lazzaro
-------------------------------------------------------------------------
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.