On Sep 6, 2011, at 6:52 PM, Chris Hanson wrote: > 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.
When did I say anything about invoking methods introduced in a later OS? If one develops an app for, say, 10.7 and has tested/validated it, but has set their SDK to Latest, then merely building it on the next generation of the OS/tools _will_ break it. Without one having made any changes to their code. > 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. It may be a very strong recommendation, but it isn't a wise one. Regards, Ken _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
