概況
我們都知道+initialize方法會在此類第一次被使用的時候會被調用，那么調用的次數是靠什么來決定的了？
結論一：類第一次被使用的時候，會先調用+initialize方法
NSObject關于initialize源碼
源碼地址: https://github.com/RetVal/objc-runtime.git
/***********************************************************************
* class_initialize. Send the '+initialize' message on demand to any
* uninitialized class. Force initialization of superclasses first.
**********************************************************************/
void _class_initialize(Class cls)
{
assert(!cls->isMetaClass());
Class supercls;
bool reallyInitialize = NO;
// Make sure super is done initializing BEFORE beginning to initialize cls.
// See note about deadlock above.
supercls = cls->superclass;
if (supercls && !supercls->isInitialized()) {
_class_initialize(supercls);
}
// Try to atomically set CLS_INITIALIZING.
{
monitor_locker_t lock(classInitLock);
if (!cls->isInitialized() && !cls->isInitializing()) {
cls->setInitializing();
reallyInitialize = YES;
}
}
if (reallyInitialize) {
// We successfully set the CLS_INITIALIZING bit. Initialize the class.
// Record that we're initializing this class so we can message it.
_setThisThreadIsInitializingClass(cls);
if (MultithreadedForkChild) {
// LOL JK we don't really call +initialize methods after fork().
performForkChildInitialize(cls, supercls);
return;
}
// Send the +initialize message.
// Note that +initialize is sent to the superclass (again) if
// this class doesn't implement +initialize. 2157218
if (PrintInitializing) {
_objc_inform("INITIALIZE: thread %p: calling +[%s initialize]",
pthread_self(), cls->nameForLogging());
}
// Exceptions: A +initialize call that throws an exception
// is deemed to be a complete and successful +initialize.
//
// Only __OBJC2__ adds these handlers. !__OBJC2__ has a
// bootstrapping problem of this versus CF's call to
// objc_exception_set_functions().
#if __OBJC2__
@try
#endif
{
callInitialize(cls);
if (PrintInitializing) {
_objc_inform("INITIALIZE: thread %p: finished +[%s initialize]",
pthread_self(), cls->nameForLogging());
}
}
#if __OBJC2__
@catch (...) {
if (PrintInitializing) {
_objc_inform("INITIALIZE: thread %p: +[%s initialize] "
"threw an exception",
pthread_self(), cls->nameForLogging());
}
@throw;
}
@finally
#endif
{
// Done initializing.
lockAndFinishInitializing(cls, supercls);
}
return;
}
else if (cls->isInitializing()) {
// We couldn't set INITIALIZING because INITIALIZING was already set.
// If this thread set it earlier, continue normally.
// If some other thread set it, block until initialize is done.
// It's ok if INITIALIZING changes to INITIALIZED while we're here,
// because we safely check for INITIALIZED inside the lock
// before blocking.
if (_thisThreadIsInitializingClass(cls)) {
return;
} else if (!MultithreadedForkChild) {
waitForInitializeToComplete(cls);
return;
} else {
// We're on the child side of fork(), facing a class that
// was initializing by some other thread when fork() was called.
_setThisThreadIsInitializingClass(cls);
performForkChildInitialize(cls, supercls);
}
}
else if (cls->isInitialized()) {
// Set CLS_INITIALIZING failed because someone else already
// initialized the class. Continue normally.
// NOTE this check must come AFTER the ISINITIALIZING case.
// Otherwise: Another thread is initializing this class. ISINITIALIZED
// is false. Skip this clause. Then the other thread finishes
// initialization and sets INITIALIZING=no and INITIALIZED=yes.
// Skip the ISINITIALIZING clause. Die horribly.
return;
}
else {
// We shouldn't be here.
_objc_fatal("thread-safe class init in objc runtime is buggy!");
}
}
先不考慮加鎖和多線程問題，_class_initialize主要的就是如下兩個步驟：
- 如果父類沒有初始化，那么遞歸初始化父類
- 初始化自己
第二步會調用:
void callInitialize(Class cls)
{
((void(*)(Class, SEL))objc_msgSend)(cls, SEL_initialize);
asm("");
}
看到objc_msgSend表明：
結論二：會走OC的消息發送流程
根據以上的推論我們可以得知：
+initialize會被調用0次，一次，多次
- 調用0次：表明這個類沒有被使用到
- 調用1次：表明只有這個類被使用到，它的子類要不然是沒有被使用到，要不然就是有這個子類自己的
+initialize(子類中+initialize中沒有[super initialize]代碼)方法 - 調用多次：表明這個類或者它的多個子類被使用了，并且這多個子類沒有自己的
+initialize方法，子類會根據OC消息發送流程而調用了它父類的+initialize方法。
或者可以這么理解，任何類在使用之前都會調用它的+initialize，如果這個類沒有+initialize，那么就找它的父類的+initialize一直到NSObject類。并且不會自動調用 [super initialize]。
Demo
為了驗證上述的結果，做了如下的測試
調用0次
類：RXInitializeParentObject 所有DemoObject的父類
@implementation RXInitializeParentObject
+ (void)initialize {
NSLog(@"Parent initialize");
}
- (void)print {
}
@end
測試類：RXInitializeTestObject
- (void)test_doNoting {
}
當然是什么也沒有輸出
調用多次
RXInitializeEmptyObject,子類沒有自己的initialize
@implementation RXInitializeEmptyObject
@end
測試類：RXInitializeTestObject
- (void)test_empty {
self.rxInitializeEmptyObject = [RXInitializeEmptyObject new];
[self.rxInitializeEmptyObject print];
}
輸出的結果：
Parent initialize
Parent initialize
第一行輸出：是因為初始化RXInitializeEmptyObject會先初始化其父類RXInitializeParentObject
第二行輸出：對于RXInitializeEmptyObject來說，根據OC的消息發送規則，它的initialize方法定位到了父類的initialize方法了
子類自定義的+initialize方法
類RXInitializeCustomObject
@implementation RXInitializeCustomObject
+ (void)initialize {
NSLog(@"Custom initialize");
}
@end
測試類：RXInitializeTestObject
- (void)test_custom {
self.rxInitializeCustomObject = [RXInitializeCustomObject new];
[self.rxInitializeCustomObject print];
}
輸出結果
Parent initialize
Custom initialize
第一行輸出：是因為初始化RXInitializeCustomObject會先初始化其父類RXInitializeParentObject
第二行輸出：對于RXInitializeCustomObject來說，它有自己的initialize方法。
先使用Empty再使用Custom
測試類：RXInitializeTestObject
- (void)test_empty_custom {
self.rxInitializeEmptyObject = [RXInitializeEmptyObject new];
[self.rxInitializeEmptyObject print];
self.rxInitializeCustomObject = [RXInitializeCustomObject new];
[self.rxInitializeCustomObject print];
}
輸出結果
Parent initialize
Parent initialize
Custom initialize
第一行輸出，是因為使用RXInitializeEmptyObject初始化其父類
第二行輸出，是因為使用RXInitializeEmptyObject初始化自己
第三行輸出，是因為使用RXInitializeCustomObject
先使用Custom再使用Empty
測試類：RXInitializeTestObject
- (void)test_custom_empty {
self.rxInitializeCustomObject = [RXInitializeCustomObject new];
[self.rxInitializeCustomObject print];
self.rxInitializeEmptyObject = [RXInitializeEmptyObject new];
[self.rxInitializeEmptyObject print];
}
輸出結果
Parent initialize
Custom initialize
Parent initialize
大家可以自己嘗試分析一下~~~
Custom & Custom2
類RXInitializeCustom2Object，內容跟RXInitializeCustomObject幾乎一樣
@implementation RXInitializeCustom2Object
+ (void)initialize {
NSLog(@"Custom 2 initialize");
}
@end
測試類：RXInitializeTestObject
- (void)test_custom_custom2
{
self.rxInitializeCustomObject = [RXInitializeCustomObject new];
[self.rxInitializeCustomObject print];
self.rxInitializeCustom2Object = [RXInitializeCustom2Object new];
[self.rxInitializeCustom2Object print];
}
輸出結果：
Parent initialize
Custom initialize
Custom2 initialize
結果也是很容易分析的。
super Custom
類RXInitializeSuperCustomObject
@implementation RXInitializeSuperCustomObject
+ (void)initialize
{
[super initialize];
NSLog(@"Super Custom initialize");
}
@end
測試類：RXInitializeTestObject
- (void)test_superCustom {
self.rxInitializeSuperCustomObject = [RXInitializeSuperCustomObject new];
[self.rxInitializeSuperCustomObject print];
}
輸出結果
Parent initialize
Parent initialize
Super Custom initialize
其中第二行是因為[super initialize]導致的。
以上就是關于+initialize方法被調用次數探究，包括理論部分和Demo部分。
