I ran into a major hurdle this week that basically stopped my work in its tracks. I've been working on moving a large codebase from an iOS app target to a framework target, since we have the same code in multiple app targets and it is problematic to have to remember to add new code to every single app target when they can all just share a framework.
However I didn't anticipate the issue that made this task explode in terms of effort. According to the Using Swift with Cocoa & obj-C book (this section: https://developer.apple.com/library/ios/documentation/Swift/Conceptual/BuildingCocoaApps/MixandMatch.html#//apple_ref/doc/uid/TP40014216-CH10-ID122), swift code in an app target can be accessed from obj-c if it is internal or public. However, swift code in a framework target can only be accessed from objc if it is public, not internal. Is there any way around this restriction? The codebase I want to migrate has a lot of swift and obj-c intermingling, and I can't see a reasonable end to converting everything I need to convert to public from internal for this to work. If there's no feasible workaround, would swift-evolution be the proper place to discuss changing this behavior? Or is this something that would need to be logged in radar for the Xcode team to address? Thanks, - Kevin _______________________________________________ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users
