Of course, any new APIs made public in Tiger will have their APIs advertised on Tiger, so a careful (daring?) developer should be able to compile against them on Tiger, or even copy just the CoreAudio related frameworks into the "10.3" SDK (or a copy, preferably!), and change their product to "requires QuickTime 7."
I'm sure this is not advisable by Apple, but I have found myself accidentally taking advantage of "available but not public" APIs in various frameworks that were available one release before they were publicized. Before the cross-compiling SDKs came out, it was easy to do this by accident because the only way to "back-target" from a newer OS was to build, test, and hope for the best. I found out only after the SDKs were added that some of my apps used "unsupported" calls on older OS releases, but worked great!
A lot of the taboo against using "private APIs" also disappears when you're using an unsupported API in an older release that has since been sanctioned. It's not like Apple is going to go back and change that release so that the calls no longer work! :)
Daniel On Apr 13, 2005, at 6:06 PM, William Stewart wrote: So, if an API is available on Panther already, with a QT update, that API will then have the same functionality as it does on Tiger.
New CA APIs, and new components are by and large only available with Tiger.
|