Re: Mapping deprecated functions to new ones
Re: Mapping deprecated functions to new ones
- Subject: Re: Mapping deprecated functions to new ones
- From: "Yves Poissant" <email@hidden>
- Date: Tue, 20 Sep 2005 15:28:06 -0400
- Organization: Hash Enterprises Inc.
From: "Finlay Dobbie" <email@hidden>
On 20/09/05, Yves Poissant <email@hidden> wrote:
In my application, the GCC compiler have reported 66 deprecated functions.
Is there a document that maps deprecated functions to the new ones I
should
use to replace those deprecated?
The documentation for the function in question normally elaborates.
I checked a couple of them and the documentation explains what they do, what
their parameters mean etc.
For some of them (not all), there is an line that mentions :
"Deprecated in Mac OS X version 10.4. Available in Mac OS X version 10.0 and
later"
None of the ones I checked pointed to which function should be used to
replace them.
What exactly is meant by "Deprecated in Mac OS X version 10.4." and then
"Available in Mac OS X version 10.0 and later"? Does that mean that it is
deprecated but it will continue to be available in the future?
Also, for some functions, there is a "Carbon Porting Notes" mentioning that
"This function is not implemented on Mac OS X." preceded by "Available in
CarbonLib 1.0 and later when running Mac OS 8.1 or later. Available in Mac
OS X version 10.0 and later.". How can it be available in Mac OS X but not
be implemented in OS X 10.4?
Yves Poissant
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden