• 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: Xcode 6 does not warn on use of iOS8 only method when deployment target is iOS7
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 6 does not warn on use of iOS8 only method when deployment target is iOS7


  • Subject: Re: Xcode 6 does not warn on use of iOS8 only method when deployment target is iOS7
  • From: Fritz Anderson <email@hidden>
  • Date: Fri, 26 Sep 2014 12:49:53 -0500

On 26 Sep 2014, at 12:01 PM, Chris Hanson <email@hidden> wrote:

> On Sep 26, 2014, at 9:06 AM, Sean McBride <email@hidden> wrote:
>>
>> If one of those buildbots fails to build because you committed something that uses new API, you find out pretty shortly thereafter.
>
> How do you actually go about using newer API when running on a newer OS with such a setup?
>
> -- Chris

We may be talking at cross-purposes.

1. It is a rational use of a developer’s time, especially a resource-constrained one, not to use newer API at all. I grant that this yields behavior that may be deprecated, or worse, but it’s more practical for many developers to address the issue case-by-case rather than across-the-board (or, only when the app breaks in the field).

2. The serial all-SDKs builds wouldn’t be for producing a release article. They would be only to flag the inadvertent use of API that would crash the product for a significant share of the developer’s customers. Whether that share is significant, or deserves service, is a question for the developer, not (with the best will in the world) Apple.

3. I’ve already alluded to why the ideal solutions are unrealistic for most developers. Audits and 100% test and QA coverage are the gold standard, but a guy working spare-time with $3000 capital can’t do it. Culturally, everybody, including Apple, wants that guy to succeed.

If you really do expect a comprehensive audit, don’t we have computers for that? For cheaper than renting a commercial build farm? **Naïvely**, I’d have thought the availability macros, which include version-of-introduction, might provide a clue.

	— F


 _______________________________________________
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


References: 
 >Xcode 6 does not warn on use of iOS8 only method when deployment target is iOS7 (From: David Hoerl <email@hidden>)
 >Re: Xcode 6 does not warn on use of iOS8 only method when deployment target is iOS7 (From: Fritz Anderson <email@hidden>)
 >Re: Xcode 6 does not warn on use of iOS8 only method when deployment target is iOS7 (From: Sean McBride <email@hidden>)
 >Re: Xcode 6 does not warn on use of iOS8 only method when deployment target is iOS7 (From: Chris Hanson <email@hidden>)

  • Prev by Date: Re: Xcode 6 does not warn on use of iOS8 only method when deployment target is iOS7
  • Next by Date: Re: Xcode 6 does not warn on use of iOS8 only method when deployment target is iOS7
  • Previous by thread: Re: Xcode 6 does not warn on use of iOS8 only method when deployment target is iOS7
  • Next by thread: Re: Xcode 6 does not warn on use of iOS8 only method when deployment target is iOS7
  • Index(es):
    • Date
    • Thread