[swift-users] New Swift development snapshots available!

New Swift snapshots available! Download new packages from https://swift.org/download/ Swift Development: (master) Following repository are tagged with swift-DEVELOPMENT-SNAPSHOT-2016-03-24-a https://github.com/apple/swift

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

Awesome, many thanks :) *___* *James⎥Head Of CEO* *ja...@supmenow.com ⎥supmenow.com * *Sup* *Runway East * *10 Finsbury Square* *London* * EC2A 1AF * On Thu, Mar 24, 2016 at 6:00 PM, Jordan Rose wrote: > Yes, with a type. So either > >

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

Yes, with a type. So either static NSString * const kAPI_ENDPOINT = @ API_ENDPOINT; or static const char *kAPI_ENDPOINT = API_ENDPOINT; Jordan > On Mar 24, 2016, at 10:55, James Campbell wrote: > > Okay that helps, in my case the macros contain mostly strings. API Keys, > Endpoints and secr

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

Okay that helps, in my case the macros contain mostly strings. API Keys, Endpoints and secrets. So something like this should work ? static const kAPI_ENDPOINT = API_ENDPOINT which will then be imported into Swift as: let endpoint = kAPI_ENDPOINT *___* *James⎥

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

I'm not sure what I would recommend; it depends what you're using this for. If it's C-style conditional compilation, Swift's own similar-but-more-limited #if and -D flags are more powerful…but then you need to maintain two sets of flags. If it's constant integer values, typed constants (using 's

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

On 3/24/16 14:05, Jordan Rose via swift-users wrote: > Ahh. Yes, we were. We would define the macro in Clang, then when we > do a lookup we'd get it back out in Swift. I, um, wouldn't have > considered that intentional, but clearly people are depending on it. I'm not following the macro issue as c

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

Yeah I noticed that it only works in Xcode 7.2 when you have a bridging header and in Xcode 7.3 if it's explicitly declared in code and you have a bridging header. Is there a way we could bring this back for a Swift 2.2.1 ? It eased our migration from Objective-C. If the recommended path is to ha

Re: [swift-users] Swift.org RSS Feed appears broken

Hi Neil, Aside from the encoding issue (which we are looking into), this should now be fixed. Can you check on your end? Thanks, Ted > On Mar 22, 2016, at 5:53 AM, Neil via swift-users > wrote: > > Hello all, > > What is the correct place to report that swift.org rss feeds are broken? The

Re: [swift-users] libswift frontend ios

> On Mar 24, 2016, at 6:12 AM, Ramakrishna Mallireddy > wrote: > > This may be due to the fact my native OSX being an 64bit architecture. Only a > 64bit compiler build work on it properly. > To make simulator i386 build works properly it may required native 32bit > architecture OSX. > > Plea

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

The reason this wouldn't have been considered intentional is because it only works for targets with bridging headers. Frameworks? Nope. Pure Swift targets? Nope. Jordan > On Mar 24, 2016, at 10:05 , Jordan Rose wrote: > > Ahh. Yes, we were. We would define the macro in Clang, then when we do

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

Ahh. Yes, we were. We would define the macro in Clang, then when we do a lookup we'd get it back out in Swift. I, um, wouldn't have considered that intentional, but clearly people are depending on it. Sorry, James! Doug, we saw a similar issue with macros in bridging headers, right? Do you reme

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

Explained in rest of the thread. It seems that in Xcode 7.2 if you specified a C Macro in the build settings it was imported (i.e API_VERSION=2). However in Xcode 7.3, only ones specified in code are imported *not* ones specified in a build setting. *___* *James⎥He

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

What macros? Swift doesn’t have macros - thanks the lord... Jan Neumüller -- GPG/PGP-Key: http://www.slayers.de/transfer/Jan_GPG_pub.asc > On 23.03.2016, at 17:43, James Campbell via swift-users > wrote: > > We are experiencing an issue when compiling swift code under Xcode 7.3. > > Preproce

Re: [swift-users] Swift and the new 2.2 release (Linux)

> On Wednesday, March 23, 2016 8:33 PM, louislepegue via swift-users > wrote: > Where is the Swift Linux compiler? /swift-2.2-RELEASE-ubuntu15.10/usr/bin/swiftc ___ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listi

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

(+Jordan) Jordan, did something change here? Were we previously getting these via the Clang importer in a way we aren't anymore? - Daniel > On Mar 24, 2016, at 9:02 AM, James Campbell wrote: > > I've just attached one now. The preprocessor macro is specified in the build > settings. > > In

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

I've just attached one now. The preprocessor macro is specified in the build settings. In Xcode 7.2 these were imported and worked like they did in C i.e API_VERSION=2 would be imported as a constant named API_VERSION and would be a 2 In Xcode 7.3 it broke. *___*

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

Swift has never supported referring directly to macros, it only supports "build configurations". I'm still not sure exactly what you have that could have worked previously. Can you please attach a complete project showing something which worked in 7.2 and does not work now to the bug you filed?

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

To hold keys and api endpoints. In the past for Objective-C I would have used it like this: request.api_endpoint = MY_MACRO_ENDPOINT And then when Swift was released I was able to do it in Xcode 7.2: request.api_endpoint = MY_MACRO_ENDPOINT But when using Xocde 7.3 I get this: request.api_end

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

> On Mar 24, 2016, at 5:21 AM, James Campbell wrote: > > This is the "GCC_PREPROCESSOR_DEFINITIONS" build setting. This previously > imported into swift. But in Xcode 7.3 it no longer does this. Ok, and exactly how are you trying to use them? Via an #if in C or via an #if in Swift? - Daniel

Re: [swift-users] libswift frontend ios

This may be due to the fact my native OSX being an 64bit architecture. Only a 64bit compiler build work on it properly. To make simulator i386 build works properly it may required native 32bit architecture OSX. Please correct me if I am wrong. Thanks Ramakrishna M On Thu, Mar 24, 2016 at 12:25 A

Re: [swift-users] Serious Issue with Project Preprocessor Build Setting, Xcode 7.3 and Swift.

This is the "GCC_PREPROCESSOR_DEFINITIONS" build setting. This previously imported into swift. But in Xcode 7.3 it no longer does this. If I write the Macros in the bridging header they are imported but I would ideally like to keep them in a build setting. *___* *

[swift-users] ClangImporter /var/temp dir settings..

How to change the temp dir path: /var/tmp/, can I input my desired path as a command argument during swift compiler invocation. Thanks Ramakrishna M ___ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users