time. Do not hold on to them past the duration of the current function, or stow them away inside structs. If you need to keep the object for longer than that, you have to either keep it or make your own into C++ exceptions. 5.1.3 Class-aware C++ API C++ wrapper classes wrap most fz_* and pdf_* C structs. • Class names are camel-case versions of the wrapped struct’s name, for example fz_document’s wrapper class is mupdf::FzDocument. • Classes automatically handle reference counting of the underlying C structs, so there is no need for manual calls to fz_keep_*() and fz_drop_*(), and class instances can be

time. Do not hold on to them past the duration of the current function, or stow them away inside structs. If you need to keep the object for longer than that, you have to either keep it or make your own into C++ exceptions. 7.1.3 Class-aware C++ API C++ wrapper classes wrap most fz_* and pdf_* C structs. • Class names are camel-case versions of the wrapped struct’s name, for example fz_document’s wrapper class is mupdf::FzDocument. • Classes automatically handle reference counting of the underlying C structs, so there is no need for manual calls to fz_keep_*() and fz_drop_*(), and class instances can be

time. Do not hold on to them past the duration of the current function, or stow them away inside structs. If you need to keep the object for longer than that, you have to either keep it or make your own into C++ exceptions. 7.1.3 Class-aware C++ API C++ wrapper classes wrap most fz_* and pdf_* C structs. • Class names are camel-case versions of the wrapped struct’s name, for example fz_document’s wrapper class is mupdf::FzDocument. • Classes automatically handle reference counting of the underlying C structs, so there is no need for manual calls to fz_keep_*() and fz_drop_*(), and class instances can be

time. Do not hold on to them past the duration of the current function, or stow them away inside structs. If you need to keep the object for longer than that, you have to either keep it or make your own into C++ exceptions. 8.2.3 Class-aware C++ API C++ wrapper classes wrap most fz_* and pdf_* C structs: • Class names are camel-case versions of the wrapped struct’s name, for example fz_document’s wrapper class is mupdf::FzDocument. • Classes automatically handle reference counting of the underlying C structs, so there is no need for manual calls to fz_keep_*() and fz_drop_*(), and class instances can be

The C++ implementation will create expressive API calls through utilizing combination of : ▪POD structs -- structs with data members only ▪designated initializers -- initializing a struct with: { .field = the road state -- There is only one. // the .= syntax is a designated initializer used to assign POD values auto result = processCarStateTransition({ .car = Car::FastSportsCar, .startingRoadState nextRoadState = { .type = RoadType::Avenue,.speed = Speed::NORMAL}}); Ambiguity The following structs will in theory dispatch to processCarStateTransition depending on how you call them. Non-Ambiguous

14 Aside: POD Types  Standard-layout types are defined in C++11.  The 2003 Standard didn’t mention standard-layout types — it describes layout guarantees in terms of POD types.  POD stands for “Plain (There’s also a POF.)  A POD is a standard-layout class that also lacks:  private or protected non-static data members  user-declared constructors  base classes  In practice, POD classes are too restrictive Type type_; short x_, y_; }; void draw(Shape *); void rotate(Shape *, int);  Here, we’re using structs and non-member functions.  We could just as well use classes and static member functions. 97 Copyright

constructor, destructor, or copy assignment operator… This definition is essentially the same as a C++03 POD type. armv7-a System V x86 System V x86 Microsoft A Composite Type not larger than 4 bytes is returned 16 bytes x86 System V fundamental only x86-64 Microsoft 1,2,4,8 bytes, C++03 POD x86 Microsoft 1,2,4,8 bytes, C++03 POD Composite types are required to be “trivial” to get into registers!C.20: If you ___$ReturnUdt$[esp-4] mov DWORD PTR [eax], 60 mov DWORD PTR [eax+4], 0 ret 0 C H R 67 not a POD not a POD size > 4 not fundamentalCan we do something about it? ● std::chrono would have to give up encapsulation

to either Kotlin enum or integral values, depending on heuristics and the de�nition �le hints. Structs / unions are mapped to types having �elds available via the dot notation, i.e. someStructInstance simple immutable self-contained value. Think C++ references, as a similar concept. For structs (and typedef s to structs) this representation is the main one and has the same name as the struct itself, for runtime by calling kotlin.native.initRuntimeIfNeeded() . Scope-local pointers Passing and receiving structs by value — — Callbacks Passing user data to callbacks 405 Often C APIs allow passing some user

CocoaPods Gradle plugin Update Podfile for Xcode Possible issues and solutions Add dependencies on a Pod library From the CocoaPods repository On a locally stored library From a custom Git repository project with several targets CocoaPods Gradle plugin DSL reference Enable the plugin cocoapods block pod() function Kotlin/Native libraries Kotlin compiler specifics cinterop tool specifics klib utility without being limited by platform–specific dependencies. For example, you can add dependencies on Pod libraries to the iosMain shared source set. Previously, this only worked with platform-specific libraries

互操作性 与 Swift/Objective-C 互操作性 Kotlin/Native 开发 Apple framework——教程 CocoaPods 集成 CocoaPods 概述 添加对 Pod 库的依赖 使用 Kotlin Gradle 项目作为 CocoaPods 依赖项 CocoaPods Gradle 插件 DSL 参考 Kotlin/Native 库 平台库 Kotlin/Native If you use CocoaPods integration, specify the cinterop option in the configuration block of the pod() function like this: kotlin { ios() cocoapods { summary = "CocoaPods test library" homepage = "https://github.com/JetBrains/kotlin" ios.deploymentTarget = "13.5" pod("PodName") { extraOpts = listOf("-compiler-option", "-fmodules") } } }