Re: How to get warnings for missing methods in older SDKs
Re: How to get warnings for missing methods in older SDKs
- Subject: Re: How to get warnings for missing methods in older SDKs
- From: Ben Staveley-Taylor <email@hidden>
- Date: Fri, 25 Mar 2011 10:46:43 +0000
Fair points. Knowing that Apple engineers read this list I'll just voice my opinion that it was way too soon to drop support for 10.5 in Xcode 4, and it has not been helpful to commercial developers. We can debate what would be an appropriate timeframe, but since the 10.5 -> 10.6 upgrade is not automatic or free it's not reasonable to tell users who bought new Macs as recently as August 2009 that they can't run your software, unless you're doing something particularly wizzy with new technologies (which sadly I'm not!)
Please, Apple, make the 10.5 SDK officially available for XCode 4, and don't drop old SDK support so soon again in future.
-- Ben.
On 25 Mar 2011, at 10:27, Quincey Morris wrote:
> So this issue isn't that the compiler doesn't support the kind of checking the OP asked for, the issue is that Xcode 4 dropped support for the 10.5 SDK. Since it did that, the best you can do is continue to use Xcode 3.2.x for apps that are written "for" 10.5.
>
> Regarding the issue of dropping 10.5 SDK support at some point in the Xcode version time, I know it's likely to be controversial, but I'd say that it's up to developers to move their users along. Good as Leopard was for developers, it's pretty old now, and Lion is just around the corner.
_______________________________________________
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