Re: Where to look for the replacement for a deprecated API?
Re: Where to look for the replacement for a deprecated API?
- Subject: Re: Where to look for the replacement for a deprecated API?
- From: Chris Hanson <email@hidden>
- Date: Sun, 15 Dec 2013 23:15:31 -0800
On Dec 9, 2013, at 2:02 PM, Jens Alfke <email@hidden> wrote:
On Dec 9, 2013, at 1:48 PM, Beinan Li < email@hidden> wrote: So I'm asking about a general strategy for the deprecation and replacement issue.
The compiler allows the deprecation marker to have a textual message that shows up in the warning you receive. I’ve seen this used in some Apple APIs, but not in all of them. (It might be a newer Clang feature?) In that case you will see in the warning some indication of what API to use instead.
Keep in mind that there’s also not always a 1:1 substitution between deprecated and non-deprecated API. The best question to ask is not “With what API should I replace this deprecated API?” but rather “What does the subsystem where this deprecated API is used do, and how should it be done now?”
Sometimes that might mean simple replacement, other times that might mean re-architecting around an entirely different mechanism.
-- Chris
|
_______________________________________________
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