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 <jim.ad...@sas.com> 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 <t...@verizon.net> 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 <wsqui...@satx.rr.com> 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 
>>> <quinceymor...@rivergatesoftware.com> wrote:
>>> 
>>>> On Jun 25, 2016, at 12:57 , Quincey Morris 
>>>> <quinceymor...@rivergatesoftware.com> 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 (Cocoa-dev@lists.apple.com)
>>> 
>>> 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:
>>> https://lists.apple.com/mailman/options/cocoa-dev/ttw4%40verizon.net
>>> 
>>> This email sent to t...@verizon.net
>> 
>> 
>> _______________________________________________
>> 
>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>> 
>> 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:
>> https://lists.apple.com/mailman/options/cocoa-dev/jim.adams%40sas.com
>> 
>> This email sent to jim.ad...@sas.com
> 


_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to