I’m writing a Swift API to an existing C library. The coding is going fine, but when I try to view the raw Swift equivalent of any of the library’s .h files (by switching the assistant editor to "Counterparts > foo.h (Interface)”), almost none of it shows up. It shows nothing but comments, then one struct declaration, and then it cuts off.
Fortunately the Swift compiler seems to understand the C API perfectly well, so my Swift code that calls it compiles fine. It’s just the display of the translated C header that fails. I assume this is a SourceKit failure?) I’ll file a Radar including the preprocessed .h file, but in the interim, does anyone have any tips & tricks for how to work around this? Like, are there any specific C syntactic features that are known to screw up SourceKit’s translator? —Jens PS: Xcode 7.3 on OS X 10.11.4. _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
