Objective-C iOS Development for Legacy & Enterprise Apps · 课时

自动引用计数（ARC）

探索 ARC 如何简化内存管理，以及它对 Objective-C 开发和旧代码的影响。

自动引用计数（ARC） 是 CoddyKit 上的免费 Objective-C iOS Development for Legacy & Enterprise Apps 课时。这是第 2 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Objective-C iOS Development for Legacy & Enterprise Apps 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Objective-C iOS Development for Legacy & Enterprise Apps 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Welcome to ARC

Memory management is crucial in programming. In Objective-C, you once had to manage memory manually, which could lead to errors like memory leaks or crashes.

Automatic Reference Counting (ARC) changed this by automating a lot of the work for you. It's a compiler feature, not a runtime garbage collector.

ARC: Compiler Magic

With ARC, the Xcode compiler automatically adds the necessary memory management code (like retain, release, and autorelease calls) into your app during compilation.

This means you no longer write these calls yourself. The compiler ensures objects are kept alive as long as they're needed and released when they're not.

Your First ARC Object

Let's see ARC in action. When you create an Objective-C object, ARC automatically manages its memory. You don't need to call release.

This simple example shows an NSString being created. ARC handles its deallocation when it's no longer referenced.

#import <Foundation/Foundation.h>

int main(int argc, const char * argv[]) {
    @autoreleasepool {
        // Create an NSString object
        NSString *greeting = @"Hello, CoddyKit!";
        NSLog(@"%@", greeting);

        // ARC automatically manages the memory for 'greeting'.
        // No explicit [greeting release] is needed here.
    }
    return 0;
}

Properties & Strong References

When you declare properties for your objects, ARC uses strong references by default for Objective-C objects. A strong reference means the object is "owned" and will not be deallocated as long as there's at least one strong reference to it.

For primitive types (like int, float), you'd use assign.

#import <Foundation/Foundation.h>

@interface MyObject : NSObject
@property (strong, nonatomic) NSString *name;
- (void)sayHello;
@end

@implementation MyObject
- (void)sayHello {
    NSLog(@"Hello, my name is %@", self.name);
}
// dealloc is called automatically when strong refs are gone
- (void)dealloc {
    NSLog(@"MyObject %@ is deallocated.", self.name);
}
@end

int main(int argc, const char * argv[]) {
    @autoreleasepool {
        MyObject *obj = [[MyObject alloc] init];
        obj.name = @"Coddy"; // 'name' is a strong property
        [obj sayHello];
        // 'obj' goes out of scope, ARC releases it, dealloc is called.
    }
    return 0;
}

Custom Cleanup with `dealloc`

Under ARC, you do not call [super dealloc] or release objects within your dealloc method. The compiler handles all Objective-C object releases.

You still use dealloc to clean up non-Objective-C resources, such as Core Foundation objects, C++ objects, or file handles.

#import <Foundation/Foundation.h>

@interface MyResourceHolder : NSObject
@property (strong, nonatomic) NSString *identifier;
@end

@implementation MyResourceHolder
- (instancetype)init {
    self = [super init];
    if (self) {
        _identifier = @"My Unique ID";
        NSLog(@"MyResourceHolder %@ created.", _identifier);
        // Imagine opening a C file handle or allocating C memory here.
    }
    return self;
}

// ARC handles Objective-C objects. Use dealloc for other resources.
- (void)dealloc {
    NSLog(@"MyResourceHolder %@ deallocated. (Closing C file handle, etc.)", _identifier);
}
@end

int main(int argc, const char * argv[]) {
    @autoreleasepool {
        MyResourceHolder *holder = [[MyResourceHolder alloc] init];
        // holder goes out of scope, ARC deallocates it.
    }
    return 0;
}

Transitioning Legacy Projects

Many older Objective-C projects were written with Manual Retain-Release (MRR). Xcode provides a tool to help migrate these projects to ARC.

Go to Edit > Refactor > Convert to Objective-C ARC.... This automates much of the conversion, but manual adjustments may still be needed, especially for complex projects or mixed codebases.

Mixed Codebases

Sometimes, you might need to use non-ARC files within an ARC project (e.g., third-party libraries). Xcode allows this.

You can tell the compiler to compile specific files without ARC by setting the -fno-objc-arc compiler flag for those files in your project's Build Phases settings.

ARC & Core Foundation

ARC only manages Objective-C objects. It doesn't manage Core Foundation objects (like CFStringRef, CFArrayRef) which are C-based.

To convert between Objective-C and Core Foundation types, you use bridging casts: __bridge, __bridge_transfer, and __bridge_retained. These tell ARC how to handle ownership.

#import <Foundation/Foundation.h>

int main(int argc, const char * argv[]) {
    @autoreleasepool {
        NSString *ocString = @"Hello ARC!";
        // __bridge_retained: transfer ownership from ARC to Core Foundation.
        // CFRelease must be called manually later.
        CFStringRef cfString = (__bridge_retained CFStringRef)ocString;

        NSLog(@"Objective-C String: %@", ocString);
        NSLog(@"Core Foundation String: %@", (__bridge NSString *)cfString);

        // Manual release required for Core Foundation objects obtained via __bridge_retained
        CFRelease(cfString);
    }
    return 0;
}

ARC's Limits & Pitfalls

While ARC simplifies memory management, it doesn't solve all problems. It can't prevent retain cycles, where two objects strongly reference each other, preventing either from being deallocated.

This is where weak references come in, which we'll cover in the next lesson. Also, be mindful of C-style memory (malloc/free) which ARC doesn't manage.

ARC Knowledge Check

ARC significantly changed how we manage memory in Objective-C.

Which of the following is a primary benefit of using Automatic Reference Counting (ARC) in Objective-C development?

ARC Recap & What's Next

You've learned that ARC automates memory management by inserting retain and release calls at compile time. This vastly simplifies development and reduces common memory errors.

We also touched on managing Core Foundation objects and the importance of using dealloc for non-Objective-C resource cleanup.

Next, we'll dive into Weak vs. Strong References to understand how to prevent retain cycles, a key concept even with ARC.

常见问题解答

「自动引用计数（ARC）」课时是免费的吗？

是的 — 「自动引用计数（ARC）」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Objective-C iOS Development for Legacy & Enterprise Apps 课程的其余内容，请升级到 CoddyKit PRO。 Objective-C iOS Development for Legacy & Enterprise Apps 课程共包含 4 节课。

「自动引用计数（ARC）」这节课中我会学到什么？

探索 ARC 如何简化内存管理，以及它对 Objective-C 开发和旧代码的影响。你通过在浏览器中直接运行的动手代码来练习 Objective-C iOS Development for Legacy & Enterprise Apps，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Objective-C iOS Development for Legacy & Enterprise Apps 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Objective-C iOS Development for Legacy & Enterprise Apps 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 2 节课，共 4 节。

「自动引用计数（ARC）」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Objective-C iOS Development for Legacy & Enterprise Apps 课中编写并运行代码吗？

能。每节 Objective-C iOS Development for Legacy & Enterprise Apps 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Objective-C iOS Development for Legacy & Enterprise Apps