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: Alexander von Below <email@hidden>
- Date: Fri, 25 Mar 2011 12:02:20 +0100
Am 25.03.2011 um 11:27 schrieb Quincey Morris:
> On Mar 25, 2011, at 02:51, Alexander von Below wrote:
>
>> The compiler COULD know about this (with all the funky availability attributes and stuff), why isn't it talking?
>
> if you were compiling against 10.6 but deploying to 10.5+, it was intended that you'd write code for 10.6 and provide alternative run-time code paths if you happened to be running on 10.5.
Correct. I am absolutely aware of this, and have been doing this for years. However, my complaint is that with Xcode 4, I have no compile-time way of making sure I did not miss a spot. Only full-coverage testing on an old system will tell me. Pardon my language, but this sucks.
> *Of course* the argument, "We don't want to shut out any potential new customers, or lose any existing customers, who might be using older Macs" is valid (and many developers are still supporting Tiger based on the same argument). But trying to get unstuck from the past is valid too. It seems to me there's no correct answer to this conflict
There used to be a good answer: I would support older OS Versions as long as I could painlessly do so. Now, it is not even painless to support OS X n -1. And, IMHO, that is losing too many people too fast.
Alex
_______________________________________________
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