Re: exposing only what you want - headers and Swift?
Re: exposing only what you want - headers and Swift?
- Subject: Re: exposing only what you want - headers and Swift?
- From: Quincey Morris <email@hidden>
- Date: Sun, 26 Jun 2016 12:00:47 -0700
- Feedback-id: 167118m:167118agrif8a:167118s2x54ZF2sB:SMTPCORP
On Jun 26, 2016, at 11:48 , William Squires <email@hidden> wrote:
>
> 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
No, only the public symbols would be in the module/framework. All the internal/private symbols have already been compiled and linked, so they’re not present any more. This also means that internal/private symbols won’t appear in a generated interface in the assistant pane.
(In fact, *within* a framework, when you’re working in Xcode, generated interfaces only show what’s accessible from your current source file. So, typically, you’ll only see the “internal” and “public” declarations.)
Of course, if the framework has debug information, the private symbols would be described there, but the *compiler* wouldn’t know anything about them.
_______________________________________________
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