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: Jens Alfke <email@hidden>
- Date: Mon, 09 Dec 2013 14:02:25 -0800
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.
If you don’t get that, check the API docs (as you said about Debugger) … most of the time there’s information there.
In the case of Debugger(), I think you can emulate it by using the signal() system call (or one of its variants — see <signal.h>) to send a particular signal, although I’m not sure which signal is equivalent to hitting a breakpoint.
—Jens |
_______________________________________________
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