Re: Swift changes in Xcode 8
Re: Swift changes in Xcode 8
- Subject: Re: Swift changes in Xcode 8
- From: Rick Mann <email@hidden>
- Date: Tue, 30 Aug 2016 18:02:26 -0700
The problem I'm having is not the changes in the language, but in the iOS API. I can compile Swift 2.2 with a compiler flag. I can't make changes to support iOS 10 (and still build with Xcode 7, which is necessary for submitting to the App Store).
Sent from my iPhone
> On Aug 30, 2016, at 17:52, Quincey Morris <email@hidden> wrote:
>
>> On Aug 30, 2016, at 17:20 , Jens Alfke <email@hidden> wrote:
>>
>> IIRC you can’t conditionalize on the OS version
>
> No, you can, and it’s everything we always wanted for Obj-C. That is, you can test the OS version, and the compiler does proper deployment target checking. (It forces you to use conditional code when the situation requires it).
>
> However, Rick is correct. Trying to move your code forward to Swift 2.3 or later is not a good idea if you want to submit before the next Swift version is released (and Xcode 8 goes GM). This boundary is something of a special case, because of the radical nature of the changes currently being made to Swift**, and shouldn’t happen again like this. OTOH, there have been no syntax enhancements to Swift for about 2 weeks now, which suggests to me that Xcode 8 is about to go GM.
>
>
> ** In effect, the current round of changes are transforming Swift from an Apple language to a platform-neutral language.
>
> Interestingly, this involves transforming Foundation from an Apple framework to a platform-neutral framework. Foundation is basic Cocoa behavior, and Cocoa is a direct descendant of NeXTStep. Very (very, very) loosely, NeXTStep is about to go global.
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden