Re: Using deprecated methods
Re: Using deprecated methods
- Subject: Re: Using deprecated methods
- From: "Michael Ash" <email@hidden>
- Date: Sat, 5 Jul 2008 11:17:05 -0400
On Sat, Jul 5, 2008 at 8:08 AM, Keith Blount <email@hidden> wrote:
> Hi,
>
> Something that has bothered me for ages in Cocoa, but which I've always put to one side, is how to handle certain deprecated methods when supporting more than one OS. In some instances it's as simple as checking at runtime which OS is being used and using the appropriate method accordingly, but I'm wondering here about the trickier instances.
Generally, just use them.
I think you're overstating the effects of having a method be
deprecated. It is not a big "EJECT!" warning that suddenly lights up.
It's more like a "service engine soon" light. You can keep driving
until the parts start to fall off the car, it's just better if you're
able to get it looked at sooner.
Likewise, "deprecated" just means that use of the method is
discouraged, particularly in new code. The reason that they are
deprecated and not simply removed is so that old code continues to
work. Generally deprecated code isn't removed for a very long time, if
ever. If you look at APIs that have been deprecated in the past,
they've failed to jump transitions that break binary compatibility
(like 64-bit), but otherwise stick around.
Sometimes, like in this particular case, the method is discouraged
because its use now has some sort of negative impact on the
application. In that case you should analyze how much work it will be
to take the dual-method approach described in this thread and whether
that work is worthwhile to overcome the negative impact.
Mike
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden