4 ms·
Is it not possible that all this fuss is over a typo? > 3.3.1 — Applications may only use Documented APIs in the manner prescribed by Apple and must not use or
by apinstein 17y ago
Is it not possible that all this fuss is over a typo?
> 3.3.1 — Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).
My thought on what they probably meant:
> 3.3.1 — Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and code written in C, C++, and Objective-C may compile and directly link only against the Documented APIs (e.g., Applications that link to UnDocumented APIs through an intermediary translation or compatibility layer or tool are prohibited).
I bet what they're trying to do is prevent intermediate tools from allowing people to "whitewash" private API access.
I say this because the interpretation everyone else is seeing in this clause is obviously a horrible position, and I just don't think that's the intent.
Time will tell!