Re: Help understanding Apple's approach in documentation a little better.
Re: Help understanding Apple's approach in documentation a little better.
- Subject: Re: Help understanding Apple's approach in documentation a little better.
- From: Marco S Hyman <email@hidden>
- Date: Sun, 16 Aug 2015 16:17:25 -0700
>
> If the debugger's variable pane exposes it, it's misleading if it doesn't somehow indicate that it's not for the developer to access.
It is there for the developer to access -- when debugging. Might even be useful. I sometimes find the information useful when trying to understand how something is put together. But don’t use it for development.
> At the least, it's confusing, because the docs say it's not supposed to be there, yet there it is.
The docs say no such thing or did I miss explicit statements that only documented methods and properties will ever exist? I think Ken is correct in saying "Their non-presence in the documentation and headers” is what shows them as private. Private is not that same as “not supposed to be there”.
_______________________________________________
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