On Sep 6, 2014, at 11:21 AM, Andreas Gustafsson <email@hidden> wrote:
But are they documented anywhere? If not, they are of no use to me, both because relying on undocumented features is a bad idea in general and because the Developer Program Agreeement specifically requires applications to only use Documented APIs.
Hi. I'm guessing you're new to Core Audio? If so, welcome.
So… couple things.
Undocumented != private APIs. AUComponent.h is one of the public headers you import as part of AudioUnit.framework. If you do old-fashioned framework linking in your Xcode project (as opposed to the "@import" new hotness, or Swift), you'll see this header file as part of your project, as seen here: https://alpha.app.net/invalidname/post/38235684/photo/1 . Basically, if you can find it with open-quickly (cmd-shift-O), it's public.
Some of the contents of these headers are in the Xcode documentation bundle, and some aren't, but that's a fault of Xcode's documentation, not of Core Audio. In fact, for Audio Unit properties and parameters, the comments in these header files are the *only* public documentation you'll find for their use and semantics.
This stuff isn't "undocumented". It's just "really, really crappily documented". Big difference. And even if it has no documentation comments in the header files, if it's in a public header file, it's fair game.
Hope this helps.
—Chris
|