Re: [swift-users] file io in Swift 2.2 for Linux (would like to be pointed in the right direction)

2016-06-04 Thread Matthias Zenger via swift-users
Quinn, thanks for the example. I agree that Foundation makes it easier by loading the data fully into memory. I still don't understand if it's currently actually *possible* to use non C-based solutions in Swift which use streaming. I wanted to use NSFileHandle (for a use case that requires streamin

Re: [swift-users] Discrepancy between sharing internal Swift symbols with Obj-C when in an app vs a framework target

2016-06-04 Thread Kevin Lundberg via swift-users
Its not just methods, but types themselves. Even if this was a solution I'd still have to manually fix all build issues by prepending dynamic to everything that needs it :( On 6/4/2016 2:56 PM, Austin Zheng wrote: > This is probably a solution to a different issue, but what happens if > you decla

Re: [swift-users] Discrepancy between sharing internal Swift symbols with Obj-C when in an app vs a framework target

2016-06-04 Thread Kevin Lundberg via swift-users
Our application target swift code is internal since we don't bother putting public in there as its not shared outside the app(s), obviously. The internally scoped swift code is exported to obj/c through the generated -Swift.h header when in the app target, in addition to anything marked as publi

Re: [swift-users] Discrepancy between sharing internal Swift symbols with Obj-C when in an app vs a framework target

2016-06-04 Thread Daniel Dunbar via swift-users
Unfortunately, this is a limitation of the current model for mixed Obj-C and Swift targets. The Swift code is compiled and optimized as a single module, and the only supported external entry points that result from that are the public API, which is then exposed as the "-Swift.h" header file. Ho

Re: [swift-users] Discrepancy between sharing internal Swift symbols with Obj-C when in an app vs a framework target

2016-06-04 Thread Austin Zheng via swift-users
This is probably a solution to a different issue, but what happens if you declare your "should be visible from Objective-C" swift methods as 'dynamic'? Austin > On Jun 4, 2016, at 11:55 AM, Jens Alfke via swift-users > wrote: > > >> On Jun 4, 2016, at 11:29 AM, Kevin Lundberg via swift-users

Re: [swift-users] Discrepancy between sharing internal Swift symbols with Obj-C when in an app vs a framework target

2016-06-04 Thread Jens Alfke via swift-users
> On Jun 4, 2016, at 11:29 AM, Kevin Lundberg via swift-users > wrote: > > However objc code inside the same framework as the swift code in question > should ideally be able to see internal swift symbols as well, as they are > within the same module. I agree; I didn’t realize that was your s

Re: [swift-users] Discrepancy between sharing internal Swift symbols with Obj-C when in an app vs a framework target

2016-06-04 Thread Kevin Lundberg via swift-users
The former case is what I'm concerned with. I agree that code external to the framework should only see public symbols. However objc code inside the same framework as the swift code in question should ideally be able to see internal swift symbols as well, as they are within the same module. --