Am 28.03.2011 um 22:09 schrieb Chris Hanson:
> Insisting that you MUST use an older SDK to target an older OS is - in the vast majority of cases - both incorrect and counterproductive. (I’m still looking into the cases where it’s been claimed it won’t work, which could be bugs or require documentation updates.)
But it is the only way to get compile-time warnings about APIs which are not available on my minimum deployment OS.
And we all know that the earlier you catch errors, the cheaper they are.
I am not saying that I must used a old SDK -- quite on the contrary, as I have said in this discussion, the current SDK contains machine readable hints on availability. But why is this not leveraged? It could be an optional step, just like the analyzer is an optional build step.
I know this from iOS, and it is a royal PITA, nothing less. On iOS it was worse, because compiling your code against a newer SDK would make it behave differently, but that is a different story ...
Again, the only ways I know to make sure your code runs on an older OS with the current Xcode paradigm is
a) Know the availability of each and every method by heart (which I can't)
b) Do a full coverage test of your software in QA -- which is the most expensive way to find bugs.
So please, Apple, give us a build step "Warn about possibly unavailable APIs"
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
