Re: Mapping deprecated functions to new ones
Re: Mapping deprecated functions to new ones
- Subject: Re: Mapping deprecated functions to new ones
- From: Mark Dawson <email@hidden>
- Date: Wed, 21 Sep 2005 10:24:17 -0700
The short answer, is "NO". There is no (overall) mapping of
depreciated functions to the new ones. You have to do your own
research (Carbon-dev is the best place to ask for help for that). In
some cases, the old functionality no longer exists in the new APIs
(usually this is the case because it got "lost in the cracks" and you
have to file bug reports to bring it back--again carbon-dev has
various threads on this subject). In some cases, how to do things
has changed, and there isn't always a 1-1 correspondence (I would say
that QuickDraw -> Quartz is like that).
Depreciated means "going away", but "not gone". It can also have the
meaning, "no longer supported", which means that any performance
problems won't be fixed, and no existing bugs will be fixed (some
introduced bugs still might). For example, FSSpecs are depreciated;
however, I believe that there still are a few supported APIs that
still take them. QuickDraw is depreciated, and can have much slower
performance under Tiger (because of performance improvements to
Quartz). However, there still are supported APIs that take QD
information and there probably is a good number of apps that use QD,
so it won't be going away soon.
Then there are the "don't exist" APIs, which I believe are stubs (no-
ops) such as HLock which don't do anything on OS X.
So only real option is to do research. It's important to look for
changes in functionality, too--maybe one of your routines is
"depreciated" in a routine; however, with research, you might notice
that there is a simpler/more recommended way of doing your chore--
such as in Tiger there's an FSMoveObject, which encapsulates all of
the old MoreFilesX code (I believe) for that functionality. So you
might replace not just the "depreciated" function, but many lines of
code for that case…
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?
_______________________________________________
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