31 Interoperability with Swift/Objective-C Usage Mappings Casting between mapped types Subclassing C features Export of KDoc comments to generated Objective-C headers Unsupported Kotlin/Native library Generated framework headers Garbage collection and reference counting Use the code from Objective-C Use the code from Swift Xcode and framework dependencies Next steps CocoaPods overview and object file? How do I run Kotlin/Native behind a corporate proxy? How do I specify a custom Objective-C prefix/name for my Kotlin framework? How do I rename the iOS framework? How do I enable bitcode

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 11.10Enumeration in Objective-C classes . . . . . . . . . . . . . . . . . . . . . . . . . . 167 12 Expressions 169 12.1 Expression Objective-C-related constructs. There are two kinds of Objective-C language features, discerned by a version number: Objective-C 1.0 and Objective-C 2.0. The Objective-C 1.0 language features can be enabled by adding the compiler. The Objective-C 2.0 language features can be enabled using a similar modewitch: {$modeswitch objectivec2} or the command-line option -Mobjectivec2. The Objective-C 2.0 language features

cannot be used in interfaces, Objective-C protocols and categories because all methods of an interface/protocol/- category must be public. Error: An interface, helper or Objective-C protocol or category cannot cannot contain fields Declarations of fields are not allowed in interfaces, helpers and Objective-C protocols and categories. An interface/helper/protocol/category can contain only methods and properties Error: REINTRODUCE cannot be used in objects reintroduce is not supported for objects, Objective-C classes and Objective-C protocols. Error: Each argument must have its own location If locations for arguments

Platform libraries Kotlin/Native interoperability Kotlin/Native interoperability with Swift/Objective-C CocoaPods integration Kotlin/Native Gradle plugin Coroutines Table of contents Additional and Objective-C projects On the other hand, Kotlin/Native supports interoperability to use existing libraries directly from Kotlin/Native: static or dynamic C Libraries C, Swift, and Objective-C frameworks projects written in C, C++, Swift, Objective-C, and other languages. It is also easy to use existing native code, static or dynamic C libraries, Swift/Objective-C frameworks, graphical engines, and anything

Platform libraries Kotlin/Native interoperability Kotlin/Native interoperability with Swift/Objective-C Kotlin/Native Gradle plugin Coroutines Table of contents Coroutine basics Table of contents and Objective-C projects On the other hand, Kotlin/Native supports interoperability to use existing libraries directly from Kotlin/Native: static or dynamic C Libraries C, Swift, and Objective-C frameworks existing projects written in C, C++, Swift, Objective-C, and other languages. It is also easy to use existing native code, static or dynamic C libraries, Swift/Objective-C frameworks, graphical engines, and

Swift Swift is a new programming language for iOS and OS X apps that builds on the best of C and Objective-C, without the constraints of C compatibility. Swift adopts safe programming patterns and adds modern built on the solid base of Foundation and Cocoa, has been modernized and standardized throughout. Objective-C itself has evolved to support blocks, collection literals, and modules, enabling framework adoption software development. Swift feels familiar to Objective-C developers. It adopts the readability of Objective-C’s named parameters and the power of Objective-C’s dynamic object model. It provides seamless

line: 1 print("Hello, world!") 2 // Prints "Hello, world!" If you have written code in C or Objective-C, this syntax looks familiar to you—in Swift, this line of code is a complete program. You don’t of developing in C and Objective-C. Swift provides its own versions of all fundamental C and Objective-C types, including Int for integers, Double and Float for floating-point values, Bool for Boolean don’t need to change. In addition to familiar types, Swift introduces advanced types not found in Objective-C, such as tuples. Tuples enable you to create and pass around groupings of values. You can use a

the iPhone and Mac today is based on Objective-C code, even for official Apple apps, although Swift usage is gaining traction year after year, and while Objective-C will be used for years to maintain new applications are likely going to be created with Swift. Before Apple introduced Swift, Objective-C was heavily developed to introduce new capabilities and features, but in the recent years this 5 This does not mean Objective-C is dead or not worth learning: Objective-C is still an essential tool for any Apple developer. That said, I am not going to cover Objective-C here, because we're focusing

years (absent other forces)JS & other examples Status quo language (e.g., JavaScript, C++, Objective-C) C++ examples — TypeScript Swift(A) “10%” incremental evolution-as-usual plan Default for for existing evolution JS & other examples 10% Status quo language (e.g., JavaScript, C++, Objective-C) C++ examples — C++11/14/17/20/23 TypeScript Swift ES 2-10 (except 4) C99/11/17, Python 2 examples “10” improvement, leap-forward plan 10% 10 Status quo language (e.g., JavaScript, C++, Objective-C) C++ examples — C++11/14/17/20/23 TypeScript Swift ES 2-10 (except 4) C99/11/17, Python 2

// import "changkun.de/x/gopherchina2023gogpu/gpu/mtl" /* #cgo CFLAGS: -Werror -fmodules -x objective-c #cgo LDFLAGS: -framework Metal -framework CoreGraphics #include "mtl.h" */ import "C" type involves system calls, and easiest approach is to use Cgo: /* #cgo CFLAGS: -Werror -fmodules -x objective-c #cgo LDFLAGS: -framework Metal -framework CoreGraphics #include "mtl.h" */ import "C" For involves system calls, and easiest approach is to use Cgo: /* #cgo CFLAGS: -Werror -fmodules -x objective-c #cgo LDFLAGS: -framework Metal -framework CoreGraphics #include "mtl.h" */ import "C" For