> On Aug 30, 2016, at 18:09 , Roland King wrote:
>
>
>> On 31 Aug 2016, at 09:02, Rick Mann wrote:
>>
>> 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
> On 31 Aug 2016, at 09:02, Rick Mann wrote:
>
> 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
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
On Aug 30, 2016, at 17:20 , Jens Alfke 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
> On Aug 30, 2016, at 4:41 PM, Rick Mann wrote:
>
> Here's the situation. I've got a Swift app that I've developed in Xcode
> 7/Swift 2.2. Using the legacy compatibility mode, I can try build it in Xcode
> 8, but unfortunately, a lot of the iOS API has changed (e.g.
Yeah, I considered that. There are 30 issues reported before Xcode stops
building. It's not really practical, and I can readily imagine a scenario where
it would be completely unreasonable to ask that.
Apple wants me to test Xcode 8 and ensure iOS 10 compatibility, but they sure
make it hard
So, it seems there's really no practical way to develop with Xcode 8 and still
be able to use Xcode 7 to submit my app.
Here's the situation. I've got a Swift app that I've developed in Xcode 7/Swift
2.2. Using the legacy compatibility mode, I can try build it in Xcode 8, but
unfortunately, a