Re: CoreAudio in Tiger
Re: CoreAudio in Tiger
- Subject: Re: CoreAudio in Tiger
- From: Daniel Jalkut <email@hidden>
- Date: Thu, 14 Apr 2005 20:22:09 -0700
On Apr 14, 2005, at 12:20 PM, William Stewart wrote:
No - that won't work. The binaries are different between Tiger and
Panther - we aren't just hiding functionality - what you see is
what you get.
I see - I got the wrong impression from your earlier statement that
there was no branch between Panther and Tiger, suggesting to me that
the binaries would be the same.
If it is an "SPI", it is not public; we are making no commitment to
its future. I have often seen these change between different
releases and 3rd parties have to change their code because of these
changes. Its probably one of the main reasons you will see
companies describe why their products do not work on "such and
such" a release. If you've not had these problems, then you are lucky.
I understand. That's why I was pointing out the difference in danger
when it's a case of using an SPI *only* in a past release. For
instance, there are symbols exported and functional in 10.2 that
didn't become public until 10.3. No matter how much of an SPI that
call was on 10.2, it's not dangerous to assume it will be there for
eternity (on 10.2). It's only risky to assume that private APIs will
continue to be around in *future* releases.
Daniel
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden