• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: exposing only what you want - headers and Swift?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: exposing only what you want - headers and Swift?


  • Subject: Re: exposing only what you want - headers and Swift?
  • From: Thomas Wetmore <email@hidden>
  • Date: Sun, 26 Jun 2016 18:54:12 -0400

Jim,

When you ship a Swift framework it does not contain source code. But if you want to give someone else the ability to build the framework (say because you don’t support a specific compiler version or specific ABI, or so unneeded parts can be left out), you must ship the source. Some software distributions come in binary form, some come in source form, and some come in both. But a Swift framework is what it is.

Tom Wetmore


> On Jun 26, 2016, at 5:19 PM, Jim Adams <email@hidden> wrote:
>
> Don’t you have to ship your Swift source code with a framework because of source incompatibility and ABI issues?
>
>> On Jun 26, 2016, at 3:06 PM, Thomas Wetmore <email@hidden> wrote:
>>
>> A framework does not include source. It as an opaque bundle that contains a public API and compiled code as an integrated whole.
>>
>>> On Jun 26, 2016, at 2:48 PM, William Squires <email@hidden> wrote:
>>>
>>> True, but they'd still have the source .swift file as the compiler would need this to know what symbols, identifiers, etc... there were, even if they were marked private. Whereas in ObjC, I can give someone the header and the framework, and they can't see the internals, and thus be tempted to program to an implementation (or, for that matter, myself) :)
>>>
>>> On Jun 25, 2016, at 3:11 PM, Quincey Morris <email@hidden> wrote:
>>>
>>>> On Jun 25, 2016, at 12:57 , Quincey Morris <email@hidden> wrote:
>>>>>
>>>>> provide a framework
>>>>
>>>> Sorry, just to clarify since you asked about this, a Swift language framework module only exposes things explicitly declared “public”. Things without access controls are implicitly “internal” and so not exposed in frameworks.
>>>>
>>>
>>> _______________________________________________
>>>
>>> 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
>>
>>
>> _______________________________________________
>>
>> 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
>


_______________________________________________

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


References: 
 >Re: exposing only what you want - headers and Swift? (From: William Squires <email@hidden>)
 >Re: exposing only what you want - headers and Swift? (From: Thomas Wetmore <email@hidden>)
 >Re: exposing only what you want - headers and Swift? (From: Jim Adams <email@hidden>)

  • Prev by Date: Re: exposing only what you want - headers and Swift?
  • Next by Date: Re: Security with Streams
  • Previous by thread: Re: exposing only what you want - headers and Swift?
  • Next by thread: How do I get data out of NSRuleEditor?
  • Index(es):
    • Date
    • Thread