识别常见遗留模式
识别现有代码中过时的模式、手动内存管理问题和已弃用的 API。
识别常见遗留模式 是 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 节课。
本课时的部分内容尚未翻译，以英文显示。
What Are Legacy Patterns?
When working with older Objective-C codebases, you'll often encounter patterns and practices that are no longer common in modern iOS development.
Identifying these legacy patterns is the first step towards understanding, maintaining, and potentially updating the code. It helps you recognize where older memory management, API usage, or syntax might be at play.
Manual Retain-Release (MRR)
Before Automatic Reference Counting (ARC) was introduced, Objective-C developers manually managed memory using a system called Manual Retain-Release (MRR).
- When you create an object, its retain count is 1.
- Calling
retainincreases the count, indicating another owner. - Calling
releasedecreases the count. - When the retain count drops to 0, the object is deallocated.
Seeing explicit retain or release calls is a strong indicator of MRR code.
MRR in Action: Retain & Release
In MRR, if you alloc or copy an object, you are responsible for calling release on it eventually. Forgetting to release leads to memory leaks.
Try running this example to see how retain counts change:
#import <Foundation/Foundation.h>
int main(int argc, const char * argv[]) {
NSObject *myObject = [[NSObject alloc] init];
NSLog(@"Initial retain count: %lu", [myObject retainCount]);
[myObject retain]; // Increase ownership
NSLog(@"After retain, count: %lu", [myObject retainCount]);
[myObject release]; // Decrease ownership
NSLog(@"After first release, count: %lu", [myObject retainCount]);
[myObject release]; // Object deallocated here
// Do NOT access myObject after its final release!
return 0;
}The Autorelease Pool
Another key part of MRR is the autorelease pool (NSAutoreleasePool).
Objects sent an autorelease message are added to the nearest pool. When the pool is drained, it sends a release message to all objects it contains.
This pattern was often used for convenience, especially when returning objects from methods, to avoid immediate deallocation.
Autorelease Pool Example
Observe how autorelease works with an NSAutoreleasePool. The string is created and then automatically released when the pool is drained.
#import <Foundation/Foundation.h>
int main(int argc, const char * argv[]) {
NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
NSString *message = [[[NSString alloc] initWithFormat:@"Hello, %@!", @"CoddyKit"] autorelease];
NSLog(@"Message: %@", message);
// When the pool is drained, 'message' receives a release call.
[pool drain];
return 0;
}Direct Instance Variable Access
In older Objective-C code, you might see direct access to instance variables (ivars), often prefixed with an underscore (e.g., _myValue) within a class's methods.
- Legacy:
_myValue = newValue; - Modern:
self.myValue = newValue;
Modern Objective-C (especially with ARC) strongly encourages using properties (self.myValue) because they automatically handle memory management (if ARC is enabled) and can trigger Key-Value Observing (KVO).
The @synthesize Directive
Before LLVM 4.0, properties weren't automatically synthesized by the compiler. Developers had to manually add the @synthesize directive in the .m file.
Example: @synthesize myProperty = _myProperty;
Seeing @synthesize statements in a class implementation file (.m) is a good clue that the code predates automatic property synthesis, indicating it's an older codebase.
Deprecated APIs & Old Classes
Apple regularly updates its frameworks, deprecating old APIs and replacing them with newer, more capable alternatives. Identifying these can help you modernize.
Common examples of deprecated UIKit classes you might find in legacy code include:
UIAlertView(replaced byUIAlertController)UIActionSheet(replaced byUIAlertController)UIPopoverController(often replaced byUIPopoverPresentationController)
Using these indicates an older iOS target or code that hasn't been updated.
Legacy Collection Syntax
Modern Objective-C provides convenient literal syntax for creating strings, numbers, arrays, and dictionaries. Older code uses more verbose factory methods.
Spotting methods like [NSString stringWithFormat:...] for simple strings, or [NSArray arrayWithObjects:...] without the @[] syntax, points to older coding styles.
#import <Foundation/Foundation.h>
int main(int argc, const char * argv[]) {
// Legacy string creation
NSString *oldStyleString = [NSString stringWithFormat:@"Hello, %@!", @"World"];
NSLog(@"Old String: %@", oldStyleString);
// Legacy array creation
NSArray *oldStyleArray = [NSArray arrayWithObjects:@"Apple", @"Banana", @"Cherry", nil];
NSLog(@"Old Array: %@", oldStyleArray);
// Modern literal equivalents (for comparison)
NSString *newStyleString = @"Hello, World!";
NSArray *newStyleArray = @[@"Apple", @"Banana", @"Cherry"];
return 0;
}Identify the Legacy Pattern
Which of the following code snippets most strongly indicates the use of Manual Retain-Release (MRR)?
Recap: Spotting Legacy Code
Great job! You've learned to identify common indicators of legacy Objective-C code:
- Manual Memory Management: Explicit
retain,release,autoreleasecalls andNSAutoreleasePool. - Property Synthesis: The presence of
@synthesizestatements. - Direct IVAR Access: Accessing instance variables directly (e.g.,
_myVar) instead of properties (self.myVar). - Deprecated APIs: Usage of older classes like
UIAlertView. - Verbose Collection Syntax: Using factory methods (e.g.,
[NSArray arrayWithObjects:...]) instead of modern literals.
Recognizing these patterns is crucial for navigating and planning updates in older codebases.
常见问题解答
「识别常见遗留模式」课时是免费的吗？
是的 — 「识别常见遗留模式」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Objective-C iOS Development for Legacy & Enterprise Apps 课程的其余内容，请升级到 CoddyKit PRO。 Objective-C iOS Development for Legacy & Enterprise Apps 课程共包含 4 节课。
「识别常见遗留模式」这节课中我会学到什么？
识别现有代码中过时的模式、手动内存管理问题和已弃用的 API。 你通过在浏览器中直接运行的动手代码来练习 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 节。
「识别常见遗留模式」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Objective-C iOS Development for Legacy & Enterprise Apps 课中编写并运行代码吗？
能。每节 Objective-C iOS Development for Legacy & Enterprise Apps 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。