3 ms·
> So why not just write the Objective-C part in C rather than calling the underlying machinery directly. Because the "underlying machinery" isn't documented by
by duskwuff 9y ago
> So why not just write the Objective-C part in C rather than calling the underlying machinery directly.
Because the "underlying machinery" isn't documented by Apple. It may not even be a stable interface!
- ssalazar 9y agoIn fact it basically is: https://developer.apple.com/documentation/objectivec/objective_c_runtime https://developer.apple.com/documentation/objectivec/objecti...
- duskwuff 9y agoMy understanding of the parent post was that they meant whatever "underlying machinery" AppKit is calling into -- not just the ObjC runtime.
- vlovich123 9y agoI typo'ed. I meant to say why not right the Objective-C part in Objective-C. I see no value in writing it all in C because you lose all the compile-time checks the compiler is able to perform to catch bugs & the C interface, which AFAIK is ABI stable (would have to be since apps are forward-compatible), is really difficult to use.