Frameworks & Modules

最新推荐文章于 2025-02-04 10:37:52 发布

chuanyituoku

最新推荐文章于 2025-02-04 10:37:52 发布

阅读量776

点赞数

CC 4.0 BY-SA版权

分类专栏： iOS 文章标签： frameworks

本文链接：https://blog.youkuaiyun.com/chuanyituoku/article/details/13276331

iOS 专栏收录该内容

94 篇文章

订阅专栏

本文介绍了iOS应用开发中常用的UIKit、Foundation及CoreGraphics等框架的作用与特点，并探讨了Xcode5之后引入的模块化概念如何简化开发流程。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

UIKit

Cocoa classes that are specialized for iOS, whose names begin with “UI,” are part of the UIKit framework. The UIKit framework is imported (<UIKit/UIKit.h>) in the precompiled header file

Foundation

Many basic Cocoa classes, such as NSString and NSArray and others whose names begin with “NS,” are part of the Foundation framework. The Foundation framework is imported in the precompiled header file, but there is no need for this, because many headers imported by UIKit.h import the Foundation framework (<Foundation/Foundation.h>). In turn, Foundation.h includes the Core Foundation headers (<CoreFoundation/CoreFoundation.h>) and loads the Core Foundation framework as a subframework; thus, there is no need for you to import or link explicitly to the Core Foundation framework (which is full of functions and pointer types whose names begin with “CF,” such as CFStringRef).

Core Graphics

The Core Graphics framework defines many structs and functions connected with drawing, whose names begin with “CG.” It is imported by many UIKit headers, so you don’t need to import it explicitly.

Starting in Xcode 5 and LLVM 5.0, you can elect to make the process of using additional frameworks much simpler, by using modules

When you build an app that imports a framework header, if the information for that framework hasn’t been cached as a module, it is cached as a module at that moment. Here are some benefits of using modules:

1. Smaller code files after precompilation

When you’re using modules, however, the imported header information lives in the modules, and the length of your code files is not significantly increased by precompilation. This might also mean that your code compiles faster.

Easier, shorter imports

#import <AddressBookUI/AddressBookUI.h>

With modules, instead of the #import directive, you can use a new directive, @import (with an at-sign instead of a hash-sign), which requires only the bare name of the framework followed by a semicolon:

@import AddressBookUI;

Moreover, #imports are automatically converted to @imports, so you can express yourself either way, and your existing code using #import keeps working while taking advantage of modules.

Autolinking