0Pricing
Objective-C iOS Development for Legacy & Enterprise Apps · 강의

자동 참조 카운팅(ARC)

ARC가 메모리 관리를 간소화하는 방식과 Objective-C 개발 및 레거시 코드에 미치는 영향을 살펴봅니다.

자동 참조 카운팅(ARC)은(는) CoddyKit의 무료 Objective-C iOS Development for Legacy & Enterprise Apps 강의입니다. 이것은 4개 중 2번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 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)” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Objective-C iOS Development for Legacy & Enterprise Apps 강의 전체를 잠금 해제할 수 있습니다. Objective-C iOS Development for Legacy & Enterprise Apps 강의에는 총 4개의 강의가 포함되어 있습니다.

“자동 참조 카운팅(ARC)”에서 뭘 배우나요?

ARC가 메모리 관리를 간소화하는 방식과 Objective-C 개발 및 레거시 코드에 미치는 영향을 살펴봅니다. 브라우저에서 직접 실행하는 실습 코드로 Objective-C iOS Development for Legacy & Enterprise Apps을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

Objective-C iOS Development for Legacy & Enterprise Apps을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 Objective-C iOS Development for Legacy & Enterprise Apps은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 2번째 강의입니다.

“자동 참조 카운팅(ARC)” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 Objective-C iOS Development for Legacy & Enterprise Apps 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 Objective-C iOS Development for Legacy & Enterprise Apps 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

  1. 수동 보존-해제(MRR) 기초
  2. 자동 참조 카운팅(ARC)
  3. 약한 참조와 강한 참조
  4. 블록의 유지 순환 끊기
← Objective-C iOS Development for Legacy & Enterprise Apps(으)로 돌아가기