3 ms·
It's 2010; is there any valid reason why a web page announcing a change to another document doesn't link to that document? Assuming this[1] is it, what exactly
by ataggart 16y ago
It's 2010; is there any valid reason why a web page announcing a change to another document doesn't link to that document?
Assuming this[1] is it, what exactly counts as a "private API" per section 3.3.1. Isn't any code I write a private API, thus calls to it a are violation? And how is that compatible with the allowance in 3.3.2 to package an interpreter into the app?
[1]http://developer.apple.com/programs/terms/ios/standard/ios_standard_agreement_20100909.pdf http://developer.apple.com/programs/terms/ios/standard/ios_s...
- allwein 16y agoThis strawman comes up every time we have a discussion about the developer agreement. The section referencing "private" APIs is talking about Apple specific APIs which have not been publicly documented. In Apple nomenclature, Public="class, methods, and properties are documented in the reference library and exposed for developers to use." Private="undocumented and exposed for Apple internal purposes only". Basically, if you can find it mentioned in the documentation, you can freely use it. If you had to do a class dump or use introspection to even find the method out, it's probably private.