기존 Objective-C 코드 리팩터링
기존 Objective-C 코드의 설계, 가독성 및 유지 관리성을 개선하기 위해 고급 리팩터링 기법을 적용합니다.
기존 Objective-C 코드 리팩터링은(는) CoddyKit의 무료 Objective-C iOS Development for Legacy & Enterprise Apps 강의입니다. 이것은 4개 중 1번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Objective-C iOS Development for Legacy & Enterprise Apps 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Objective-C iOS Development for Legacy & Enterprise Apps 강의에는 총 4개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
Why Refactor Legacy Objective-C?
Welcome! In this lesson, we'll dive into refactoring legacy Objective-C codebases. Refactoring means improving the internal structure of code without changing its external behavior.
For older Objective-C apps, refactoring is crucial. It helps reduce bugs, makes the code easier to understand, and paves the way for new features and modernization.
Spotting Code Smells
Before we refactor, we need to identify areas that need improvement. These are often called 'code smells' – indicators that something might be wrong with the code's design.
- Long Methods: Methods that do too many things.
- God Objects: Classes that have too many responsibilities.
- Duplicated Code: The same logic appearing in multiple places.
- Poor Naming: Unclear variable, method, or class names.
Recognizing these helps you target your refactoring efforts.
Refactor: Extract Method
The Extract Method technique involves turning a code fragment from a larger method into its own new method. This makes the original method shorter and clearer, and the new method can be reused.
Consider this example where a single method handles multiple report generation steps:
#import <Foundation/Foundation.h>
@interface ReportGenerator : NSObject
- (void)generateDetailedReportForData:(NSArray<NSNumber *> *)data values:(NSArray<NSNumber *> *)values;
@end
@implementation ReportGenerator
- (void)generateDetailedReportForData:(NSArray<NSNumber *> *)data values:(NSArray<NSNumber *> *)values {
// Calculate sum of data
double sumData = 0;
for (NSNumber *num in data) {
sumData += [num doubleValue];
}
NSLog(@"Data Sum: %.2f", sumData);
// Calculate average of values
double sumValues = 0;
for (NSNumber *num in values) {
sumValues += [num doubleValue];
}
double avgValues = sumValues / [values count];
NSLog(@"Values Average: %.2f", avgValues);
// Check for anomalies (simplified example)
if (sumData > 100 && avgValues < 10) {
NSLog(@"Anomaly Detected.");
} else {
NSLog(@"No anomaly detected.");
}
// Log final report generation time
NSDate *now = [NSDate date];
NSLog(@"Report generated at: %@", now);
}
@end
int main(int argc, const char * argv[]) {
@autoreleasepool {
ReportGenerator *generator = [[ReportGenerator alloc] init];
NSArray<NSNumber *> *sampleData = @[@20.0, @30.0, @60.0];
NSArray<NSNumber *> *sampleValues = @[@5.0, @8.0, @7.0];
[generator generateDetailedReportForData:sampleData values:sampleValues];
}
return 0;
}Refactor: Explaining Variable
Sometimes, complex expressions can be hard to understand at a glance. The Introduce Explaining Variable refactoring creates a temporary variable to hold the result of a complex expression, giving it a clear, descriptive name.
This improves readability without changing the logic. Look at this conditional:
#import <Foundation/Foundation.h>
@interface PriceCalculator : NSObject
- (CGFloat)calculatePriceForQuantity:(NSInteger)quantity isPremiumCustomer:(BOOL)isPremium hasCoupon:(BOOL)hasCoupon;
@end
@implementation PriceCalculator
- (CGFloat)calculatePriceForQuantity:(NSInteger)quantity isPremiumCustomer:(BOOL)isPremium hasCoupon:(BOOL)hasCoupon {
CGFloat basePrice = 100.0 * quantity;
// Complex condition
if (quantity > 10 && isPremium && !hasCoupon) {
basePrice *= 0.8; // 20% discount
} else if (quantity > 5 && (isPremium || hasCoupon)) {
basePrice *= 0.9; // 10% discount
}
return basePrice;
}
@end
int main(int argc, const char * argv[]) {
@autoreleasepool {
PriceCalculator *calculator = [[PriceCalculator alloc] init];
NSLog(@"Price 1: %.2f", [calculator calculatePriceForQuantity:15 isPremiumCustomer:YES hasCoupon:NO]);
NSLog(@"Price 2: %.2f", [calculator calculatePriceForQuantity:7 isPremiumCustomer:NO hasCoupon:YES]);
}
return 0;
}Refactor: Symbolic Constants
Replace Magic Number with Symbolic Constant helps make code more understandable. A 'magic number' is a hard-coded numerical value that appears directly in the code without explanation.
Replacing these with named constants (e.g., #define or const) improves readability and makes future changes easier.
#import <Foundation/Foundation.h>
@interface ScoreEvaluator : NSObject
- (NSString *)evaluateScore:(NSInteger)score;
@end
@implementation ScoreEvaluator
- (NSString *)evaluateScore:(NSInteger)score {
// Magic numbers: 90, 75, 60
if (score >= 90) {
return @"Excellent";
} else if (score >= 75) {
return @"Good";
} else if (score >= 60) {
return @"Pass";
} else {
return @"Fail";
}
}
@end
int main(int argc, const char * argv[]) {
@autoreleasepool {
ScoreEvaluator *evaluator = [[ScoreEvaluator alloc] init];
NSLog(@"Score 95: %@", [evaluator evaluateScore:95]);
NSLog(@"Score 70: %@", [evaluator evaluateScore:70]);
}
return 0;
}Refactor: Consolidate Conditionals
When several conditional expressions lead to the same result, you can Consolidate Conditional Expression. This means combining them into a single, more concise logical expression.
It simplifies the code and reduces redundancy, making it easier to read and maintain.
#import <Foundation/Foundation.h>
@interface UserValidator : NSObject
- (BOOL)isUserEligibleForFeature:(BOOL)hasSubscription isActive:(BOOL)isActive isBetaTester:(BOOL)isBetaTester;
@end
@implementation UserValidator
- (BOOL)isUserEligibleForFeature:(BOOL)hasSubscription isActive:(BOOL)isActive isBetaTester:(BOOL)isBetaTester {
// Original logic:
if (hasSubscription) {
return YES;
}
if (isActive && isBetaTester) {
return YES;
}
return NO;
}
@end
int main(int argc, const char * argv[]) {
@autoreleasepool {
UserValidator *validator = [[UserValidator alloc] init];
NSLog(@"User 1 Eligible: %@", [validator isUserEligibleForFeature:YES isActive:NO isBetaTester:NO] ? @"YES" : @"NO");
NSLog(@"User 2 Eligible: %@", [validator isUserEligibleForFeature:NO isActive:YES isBetaTester:YES] ? @"YES" : @"NO");
NSLog(@"User 3 Eligible: %@", [validator isUserEligibleForFeature:NO isActive:YES isBetaTester:NO] ? @"YES" : @"NO");
}
return 0;
}Refactor: Move Method/Field
The Move Method and Move Field refactorings are about improving class cohesion and reducing coupling. If a method or a field in one class primarily interacts with another class, it might belong in that other class instead.
- Move Method: Relocates a method to the class where it makes most sense.
- Move Field: Moves an instance variable to the class that uses it most.
This ensures that related data and behavior are kept together.
Refactor: Extract Class
When a single class grows too large and takes on too many responsibilities, it becomes a 'God Object'. The Extract Class refactoring helps break down such a class into smaller, more focused classes, each with a single responsibility.
This improves modularity, testability, and makes the code easier to manage.
#import <Foundation/Foundation.h>
// Before (simplified God Object concept)
@interface UserProfileManager : NSObject
@property (nonatomic, strong) NSString *username;
@property (nonatomic, strong) NSString *email;
- (void)loadUserDataFromRemoteServer;
- (void)saveUserDataToLocalCache;
- (void)displayProfileOnScreen;
- (BOOL)authenticateUserWithPassword:(NSString *)password;
@end
@implementation UserProfileManager
- (void)loadUserDataFromRemoteServer { NSLog(@"Loading user data..."); }
- (void)saveUserDataToLocalCache { NSLog(@"Saving user data..."); }
- (void)displayProfileOnScreen { NSLog(@"Displaying profile..."); }
- (BOOL)authenticateUserWithPassword:(NSString *)password {
NSLog(@"Authenticating user...");
return YES;
}
@end
int main(int argc, const char * argv[]) {
@autoreleasepool {
UserProfileManager *manager = [[UserProfileManager alloc] init];
manager.username = @"coddykit";
[manager authenticateUserWithPassword:@"password"];
[manager loadUserDataFromRemoteServer];
[manager displayProfileOnScreen];
}
return 0;
}Readability: Naming & Style
Beyond structural changes, improving readability is a critical part of refactoring legacy code. This includes:
- Descriptive Naming: Use clear, concise names for classes, methods, and variables that reflect their purpose.
- Objective-C Conventions: Adhere to standard Objective-C naming conventions (e.g.,
camelCasefor variables, `CapitalizedCamelCase` for classes,- (void)doSomethingWith:(id)parameterfor methods). - Consistent Formatting: Maintain consistent indentation and code style throughout the codebase.
These practices make the code much easier for you and others to understand.
Refactoring Challenge
Refactoring helps us maintain and evolve complex applications.
Which refactoring technique best addresses a method that has grown too large and performs multiple unrelated tasks?
Lesson Recap
In this lesson, we explored key refactoring techniques for legacy Objective-C codebases:
- Identifying 'code smells' like long methods and God objects.
- Applying techniques such as Extract Method, Introduce Explaining Variable, and Replace Magic Number with Symbolic Constant.
- Improving structure with Consolidate Conditional Expression, Move Method/Field, and Extract Class.
- The importance of clear naming and consistent style.
Continuous refactoring is essential for keeping legacy apps maintainable and ready for future development!
자주 묻는 질문
“기존 Objective-C 코드 리팩터링” 강의는 무료인가요?
네 — “기존 Objective-C 코드 리팩터링” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Objective-C iOS Development for Legacy & Enterprise Apps 강의 전체를 잠금 해제할 수 있습니다. Objective-C iOS Development for Legacy & Enterprise Apps 강의에는 총 4개의 강의가 포함되어 있습니다.
“기존 Objective-C 코드 리팩터링”에서 뭘 배우나요?
기존 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개 중 1번째 강의입니다.
“기존 Objective-C 코드 리팩터링” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 Objective-C iOS Development for Legacy & Enterprise Apps 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 Objective-C iOS Development for Legacy & Enterprise Apps 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.
이 강의의 모든 강의
- 기존 Objective-C 코드 리팩터링
- 기술 부채 관리
- 장기 유지 관리 전략
- 리팩터링 전 특성화 테스트 작성