• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How to get warnings for missing methods in older SDKs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to get warnings for missing methods in older SDKs


  • Subject: Re: How to get warnings for missing methods in older SDKs
  • From: Quincey Morris <email@hidden>
  • Date: Fri, 25 Mar 2011 03:27:15 -0700

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?

There *is* an answer to this question, I think, but it won't really help:

SDKs were never intended to be used this way. That is, it was never intended that you should try to make the 10.6 SDK pretend to be 10.5. Rather, 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. Therefore, having the compiler complain about 10.6 methods made no sense -- because you would have 10.6 code in your app as well. If you wanted to deploy to 10.5+ without using anything beyond the 10.5 SDK, you were supposed compile against the 10.5 SDK.

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.

*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, except to use Xcode 3 (or both Xcode 3 and Xcode 4 as necessary) if your business model requires this kind of backward reaching support.

FWIW


 _______________________________________________
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

  • Follow-Ups:
    • Mac OS 10.5 is "pretty old now" ?
      • From: Xochitl Lunde <email@hidden>
    • Re: How to get warnings for missing methods in older SDKs
      • From: Alexander von Below <email@hidden>
    • Re: How to get warnings for missing methods in older SDKs
      • From: Ben Staveley-Taylor <email@hidden>
References: 
 >How to get warnings for missing methods in older SDKs (From: Ben Staveley-Taylor <email@hidden>)
 >Re: How to get warnings for missing methods in older SDKs (From: Alexander von Below <email@hidden>)

  • Prev by Date: Xcode 4 Console Pane
  • Next by Date: Re: How to get warnings for missing methods in older SDKs
  • Previous by thread: Re: How to get warnings for missing methods in older SDKs
  • Next by thread: Re: How to get warnings for missing methods in older SDKs
  • Index(es):
    • Date
    • Thread