Re: The best way to call Cocoa methods not implemented in previous versions of the SDK?
Re: The best way to call Cocoa methods not implemented in previous versions of the SDK?
- Subject: Re: The best way to call Cocoa methods not implemented in previous versions of the SDK?
- From: Chris Hanson <email@hidden>
- Date: Tue, 06 Sep 2011 16:52:48 -0700
On Sep 6, 2011, at 4:44 PM, Ken Thomases wrote:
> On Sep 6, 2011, at 6:31 PM, Chris Hanson wrote:
>
>> Furthermore, Xcode 3.2.6 and 4.0 added "Latest Mac OS X" and "Latest iOS" options to the Base SDK pop-up, which is preferable to specifying a particular OS version for the SDK against which you wish to build.
>
> "Preferable" only if you want unpredictable changes in behavior, as has been discussed elsewhere in this thread. One should only change the SDK being used after careful deliberation and a plan to cope with the changed behavior (possibly while also coping with the old behavior if you continue to deploy to older OS versions). Automatic switching, as embodied in those options, is an awful idea, in my opinion.
And has been discussed in the rest of the thread, you should not leave your Base SDK set to an earlier OS and then invoke methods introduced in a later OS, because the new methods may require new-OS framework behavior.
It is a very strong recommendation that you set your Base SDK to Latest and use the Deployment Target to specify the least recent OS on which your application will be run.
(This is the only choice available for iOS development.)
-- Chris
_______________________________________________
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