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 protected]> 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 protected]> wrote: > >> On Jun 25, 2016, at 12:57 , Quincey Morris >> <[email protected]> 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 protected]) > > 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 [email protected] _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
