Objective-C iOS Development for Legacy & Enterprise Apps · レッスン

Weak参照とStrong参照

retain cycleを防ぎ、オブジェクトのライフタイムを適切に管理するために、strong参照とweak参照の違いを理解します。

「Weak参照とStrong参照」はCoddyKit上の無料Objective-C iOS Development for Legacy & Enterprise Appsレッスンです。これはレッスン3/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはObjective-C iOS Development for Legacy & Enterprise Apps学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Objective-C iOS Development for Legacy & Enterprise Appsコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

Understanding Object Lifetimes

In Objective-C, managing an object's lifetime is crucial. This means deciding when an object should exist in memory and when it can be safely removed.

References are how we tell the system that we 'care' about an object and want it to stay alive. There are two main types: strong and weak.

Strong References: The Default

A strong reference is the default type for properties and variables in Objective-C when using ARC (Automatic Reference Counting).

It signifies 'ownership' of an object.
When an object has at least one strong reference, it cannot be deallocated.
It increases the object's retain count, ensuring it stays in memory.

Think of it as holding onto something tightly; as long as you hold it, it won't disappear.

Strong Reference Example

Let's see a strong reference in action. The person1 variable holds a strong reference to our Person object. Notice the dealloc method is called when the object is no longer strongly referenced.

#import <Foundation/Foundation.h>

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

@implementation Person
- (void)sayHello {
    NSLog(@"Hello, my name is %@", self.name);
}
- (void)dealloc {
    NSLog(@"Person %@ is being deallocated.", self.name);
}
@end

int main(int argc, const char * argv[]) {
    @autoreleasepool {
        Person *person1 = [[Person alloc] init];
        person1.name = @"Alice";
        NSLog(@"Person '%@' created.", person1.name);
        [person1 sayHello];
        // person1 goes out of scope at the end of @autoreleasepool
        // The Person object will be deallocated.
    }
    return 0;
}

The Problem: Retain Cycles

While strong references are essential, they can lead to a common memory management issue called a retain cycle (or strong reference cycle).

This happens when two or more objects hold strong references to each other, forming a closed loop. Because each object is strongly referenced by another in the cycle, their retain counts never drop to zero, and they are never deallocated.

Illustrating a Retain Cycle

Imagine a Parent object strongly references a Child object, and that Child object also strongly references its Parent.

Parent says: "I own Child."
Child says: "I own Parent."

Neither can be released because the other is still holding onto it, even if no other part of your app needs them anymore. This leads to a memory leak.

Introducing Weak References

Weak references (declared with __weak or the weak property attribute) are designed to break retain cycles.

They do not increase an object's retain count.
They do not signify ownership.
Crucially, a weak reference automatically becomes nil when the object it points to is deallocated.

This 'nilling out' behavior is very safe and prevents dangling pointers.

Weak Reference Behavior

Observe how a weak reference behaves. Once the last strong reference to an object is released, the object is deallocated, and any weak references pointing to it automatically become nil.

#import <Foundation/Foundation.h>

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

@implementation Person
- (void)dealloc {
    NSLog(@"Person %@ is being deallocated.", self.name);
}
@end

int main(int argc, const char * argv[]) {
    @autoreleasepool {
        Person *strongPerson = [[Person alloc] init];
        strongPerson.name = @"Bob";
        
        __weak Person *weakPerson = strongPerson;
        
        NSLog(@"Before nil: strongPerson = %@, weakPerson = %@", strongPerson.name, weakPerson.name);
        
        strongPerson = nil; // Release the strong reference
        NSLog(@"Strong reference set to nil.");
        
        if (weakPerson) {
            NSLog(@"Weak Person still exists: %@", weakPerson.name);
        } else {
            NSLog(@"Weak Person is now nil.");
        }
    }
    return 0;
}

Breaking the Retain Cycle

To break a retain cycle, one of the references in the cycle should be weak. In our Parent-Child example, it's common for the 'child' to have a weak reference to its 'parent'.

This way, the parent owns the child, but the child doesn't own the parent, allowing both to be deallocated properly.

#import <Foundation/Foundation.h>

@interface Parent : NSObject
@property (strong, nonatomic) NSString *name;
@property (strong, nonatomic) id child; // Strong ref to child
- (void)dealloc;
@end

@interface Child : NSObject
@property (strong, nonatomic) NSString *name;
@property (weak, nonatomic) Parent *parent; // Weak ref to parent
- (void)dealloc;
@end

@implementation Parent
- (void)dealloc {
    NSLog(@"Parent %@ is being deallocated.", self.name);
}
@end

@implementation Child
- (void)dealloc {
    NSLog(@"Child %@ is being deallocated.", self.name);
}
@end

int main(int argc, const char * argv[]) {
    @autoreleasepool {
        Parent *myParent = [[Parent alloc] init];
        myParent.name = @"Mom";
        
        Child *myChild = [[Child alloc] init];
        myChild.name = @"Alice";
        
        myParent.child = myChild; // Parent strongly references Child
        myChild.parent = myParent; // Child weakly references Parent
        
        NSLog(@"Parent and Child created. Releasing strong variables...");
        // Both objects will be deallocated as strong references from outside
        // the objects are released and the weak link doesn't prevent deallocation.
    }
    return 0;
}

`weak` vs. `unsafe_unretained`

You might encounter __unsafe_unretained, another non-owning reference type. However, always prefer __weak.

__weak: Automatically becomes nil when the object is deallocated, preventing crashes.
__unsafe_unretained: Does NOT become nil. If the object is deallocated, the reference becomes a dangling pointer, leading to crashes if you try to access it.

__weak is the safer and standard choice in modern Objective-C with ARC.

Check Your Knowledge

Which statement best describes the primary purpose of a weak reference in Objective-C with ARC?

Recap: Strong vs. Weak

We've explored the critical difference between strong and weak references:

Strong references: Default, signify ownership, increase retain count, keep objects alive.
Weak references: Do not signify ownership, do not increase retain count, automatically become nil, and are essential for breaking retain cycles.

Understanding when to use each is key to preventing memory leaks and writing robust Objective-C code.

よくある質問

「Weak参照とStrong参照」レッスンは無料ですか？

はい。「Weak参照とStrong参照」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Objective-C iOS Development for Legacy & Enterprise Appsコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Objective-C iOS Development for Legacy & Enterprise Appsコースには全4レッスンが含まれています。

「Weak参照とStrong参照」で何を学びますか？

retain cycleを防ぎ、オブジェクトのライフタイムを適切に管理するために、strong参照とweak参照の違いを理解します。ブラウザで直接実行するハンズオンコードでObjective-C iOS Development for Legacy & Enterprise Appsを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Objective-C iOS Development for Legacy & Enterprise Appsを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのObjective-C iOS Development for Legacy & Enterprise Appsは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン3/4です。

「Weak参照とStrong参照」レッスンにはどのくらい時間がかかりますか？

ほとんどの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に戻る