iOS底层原理 Category与关联对象本质 --(4)
上篇文章讲了KVO本质和KVC的联系，想必你们都已经清楚了，今天咱们再看一下Category的底层原理。 先看一下Category的简单使用，首先新增一个类的Category，而后添加须要的函数，而后在使用的文件中导入就能够直接使用了。代码以下:git
@interface FYPerson : NSObject
- (void)run;
@end
@implementation FYPerson
-(void)run{
NSLog(@"run is run");
}
@end
//类别
@interface FYPerson (test)
- (void)test;
@end
@implementation FYPerson (test)
- (void)test{
NSLog(@"test is run");
}
@end
//使用
#import "FYPerson.h"
#import "FYPerson+test.h"
FYPerson *person=[[FYPerson alloc]init];
[person test];
[person run];
复制代码
类别使用就是这么简单。 那么类别的本质是什么呢？类的方法是存储在什么地方呢？ 第一篇类的本质已经讲过了，运行时中，类对象是有一份，方法都存储在类对象结构体fy_objc_class中的class_data_bits_t->data()->method_list_t中的，那么类别方法也是存储在method_list_t和取元类对象的method_list_t中的。编译的时候类别编译成结构体_category_t,而后runtime在运行时动态将方法添加到method_list_t中。运行xcrun -sdk iphoneos clang -arch arm64 -rewrite-objc FYPerson+test.m -o FYPerson+test.cpp进入到FYPerson+test.cpp内部查看编译以后的代码github
struct _category_t {
const char *name; //"FYPerson"
struct _class_t *cls;
const struct _method_list_t *instance_methods;
const struct _method_list_t *class_methods;
const struct _protocol_list_t *protocols;
const struct _prop_list_t *properties;
};
//存储 test方法
static struct /*_method_list_t*/ {
unsigned int entsize; // sizeof(struct _objc_method)
unsigned int method_count;
struct _objc_method method_list[1];
} _OBJC_$_CATEGORY_INSTANCE_METHODS_FYPerson_$_test __attribute__ ((used, section ("__DATA,__objc_const"))) = {
sizeof(_objc_method),
1,
{{(struct objc_selector *)"test", "v16@0:8", (void *)_I_FYPerson_test_test}}
};
extern "C" __declspec(dllimport) struct _class_t OBJC_CLASS_$_FYPerson;
//_category_t 存储FYPerson的分类的数据
static struct _category_t _OBJC_$_CATEGORY_FYPerson_$_test __attribute__ ((used, section ("__DATA,__objc_const"))) =
{
"FYPerson",
0, // &OBJC_CLASS_$_FYPerson,
(const struct _method_list_t *)&_OBJC_$_CATEGORY_INSTANCE_METHODS_FYPerson_$_test,//instace方法
0,//类方法
0,//协议方法
0,//属性
};
复制代码
存储在_category_t中的数据是什么时间加载到FYPerson的class_data_bits_t.data呢？咱们探究一下，打开源码下载打开工程阅读源码找到objc-os.mm,经过查找函数运行顺序获得_objec_init->map_images->map_images_noljock->_read_images->remethodizeClass(cls)->attachCategories(cls, cats, true /*flush caches*/)，最终进入到attachCategories关键函数内部：bootstrap
// Attach method lists and properties and protocols from categories to a class.
// Assumes the categories in cats are all loaded and sorted by load order,
// oldest categories first.
static void
attachCategories(Class cls, category_list *cats, bool flush_caches)
{
if (!cats) return;
if (PrintReplacedMethods) printReplacements(cls, cats);
bool isMeta = cls->isMetaClass();
// fixme rearrange to remove these intermediate allocations
//方法数组[[1,2,3],[4,5,6],[7,8,9]]
method_list_t **mlists = (method_list_t **)
malloc(cats->count * sizeof(*mlists));
//属性数组
property_list_t **proplists = (property_list_t **)
malloc(cats->count * sizeof(*proplists));
//协议数组
protocol_list_t **protolists = (protocol_list_t **)
malloc(cats->count * sizeof(*protolists));
// Count backwards through cats to get newest categories first
int mcount = 0;
int propcount = 0;
int protocount = 0;
int i = cats->count;
bool fromBundle = NO;
//最后的编译文件放到最前边
while (i--) {
//取出某个分类
auto& entry = cats->list[i];
//取出分类 的 instance方法或者class方法
method_list_t *mlist = entry.cat->methodsForMeta(isMeta);
if (mlist) {
mlists[mcount++] = mlist; //mlists 接受全部分类方法
fromBundle |= entry.hi->isBundle();
}
//proplist 接受全部分类属性
property_list_t *proplist =
entry.cat->propertiesForMeta(isMeta, entry.hi);
if (proplist) {
proplists[propcount++] = proplist;
}
//proplist 接受全部协议方法
protocol_list_t *protolist = entry.cat->protocols;
if (protolist) {
protolists[protocount++] = protolist;
}
}
//收集了全部协议 分类方法
auto rw = cls->data();
prepareMethodLists(cls, mlists, mcount, NO, fromBundle);
//追加全部分类方法
rw->methods.attachLists(mlists, mcount);
//释放数组
free(mlists);
//刷新该类的缓存
if (flush_caches && mcount > 0) flushCaches(cls);
//追加全部分类属性
rw->properties.attachLists(proplists, propcount);
free(proplists);//释放数组
//追加全部分类协议
rw->protocols.attachLists(protolists, protocount);
free(protolists);//释放数组
}
复制代码
attachCategories是将全部的分类方法和协议，属性倒序添加到类中，具体添加的优先级是怎么操做的？进入到rw->protocols.attachLists内部：数组
void attachLists(List* const * addedLists, uint32_t addedCount) {
if (addedCount == 0) return;
if (hasArray()) {
// many lists -> many lists
uint32_t oldCount = array()->count;
//一共须要的数量
uint32_t newCount = oldCount + addedCount;
//分配内存 内存不够用了，须要扩容
setArray((array_t *)realloc(array(), array_t::byteSize(newCount)));
//赋值count
array()->count = newCount;
// array()->lists：原来的方法列表向后移动 oldCount * sizeof(array()->lists[0]个长度
memmove(array()->lists + addedCount/*指针移动到数组末尾*/, array()->lists/*数组*/,
oldCount * sizeof(array()->lists[0])/*移动数据的大小*/);
//空出来的 内存使用addedLists拷贝过去 大小是:addedCount * sizeof(array()->lists[0])
memcpy(array()->lists, addedLists,
addedCount * sizeof(array()->lists[0]));
/*
图示讲解：
array()->lists:A->B->C->D->E
addedCount:3
addedLists:P->L->V
memmove以后：nil->nil->nil->A->B->C->D->E
而后再讲addedLists插入到数组前边,最终array()->lists的值是：
P->L->V->A->B->C->D->E
*/
}
else if (!list && addedCount == 1) {
// 0 lists -> 1 list
list = addedLists[0];
}
else {
// 1 list -> many lists
List* oldList = list;
uint32_t oldCount = oldList ? 1 : 0;
uint32_t newCount = oldCount + addedCount;
setArray((array_t *)malloc(array_t::byteSize(newCount)));
array()->count = newCount;
if (oldList) array()->lists[addedCount] = oldList;
memcpy(array()->lists, addedLists,
addedCount * sizeof(array()->lists[0]));
}
}
复制代码
能够看出来：缓存
- 首先经过
runtime加载某个类的全部Category数据 - 把全部Category的方法，属性，协议数据合并到一个大数组中，后面参与编译的数组会出如今数组前边
- 将合并后的分类数组(方法，属性，协议)插入到类原来的数据的前面。
具体的编译顺序是project文件中->Build Phases->Complile Sources的顺序。bash
调用顺序
+load加载顺序
每一个类和分类都会加载的时候调用+load方法，具体是怎么调用呢？咱们查看源码_objc_init->load_images->call_load_methods数据结构
void call_load_methods(void)
{
static bool loading = NO;
bool more_categories;
loadMethodLock.assertLocked();
// Re-entrant calls do nothing; the outermost call will finish the job.
if (loading) return;
loading = YES;
void *pool = objc_autoreleasePoolPush();
do {
// 1. Repeatedly call class +loads until there aren't any more //执行class+load直到完成 while (loadable_classes_used > 0) { call_class_loads(); } //执行Category +load 一次 // 2. Call category +loads ONCE more_categories = call_category_loads(); // 3. Run more +loads if there are classes OR more untried categories } while (loadable_classes_used > 0 || more_categories); objc_autoreleasePoolPop(pool); loading = NO; } 复制代码
类+load在Category+load前边执行，当类的+load执行完毕而后再去执行Category+load,并且只有一次。 当class有子类的时候加载顺序呢？其实全部类都是基于NSObject，那么咱们假设按照编译顺序加载Class+load，就有一个问题是父类+load执行的操做岂不是在子类执行的时候尚未执行吗？这个假设明显不对，基类+load中的操做是第一个执行的，其余子类是按照superclass->class->sonclass的顺序执行的。 查看源码_objc_init->load_images->prepare_load_methods((const headerType *)mh)->schedule_class_load在objc-runtime-new.mm2856行app
/***********************************************************************
* Schedule +load for classes in this image, any un-+load-ed
* superclasses in other images, and any categories in this image.
**********************************************************************/
// Recursively schedule +load for cls and any un-+load-ed superclasses.
// cls must already be connected.
static void schedule_class_load(Class cls)
{
if (!cls) return;
assert(cls->isRealized()); // _read_images should realize
if (cls->data()->flags & RW_LOADED) return;
// Ensure superclass-first ordering
//递归调用本身直到调用clas->self
schedule_class_load(cls->superclass);
//添加class
add_class_to_loadable_list(cls);
cls->setInfo(RW_LOADED);
}
复制代码
能够了解到该函数递归调用本身，直到+load方法已经调用过为止，因此无论编译顺序是高低，+load的加载顺序始终是NSObject->FYPrson->FYStudent。多个类平行关系的话，按照编译顺序加载。 下边是稍微复杂点的类关系：iphone
NSObject
Person
Student
NSObjet
Car
BigCar
BigOrSmallCar
复制代码
编译顺序是ide
Person
Student
Car
BigOrSmallCar
复制代码
那么他们+load的加载顺序是：
NSobject->Person->Student->Car->BigCar->BigOrSmallCar
复制代码
看着不是很明白的 能够再看一下刚才的schedule_class_load函数。 加载成功以后，是按照objc_msgsend()流程发送的吗？咱们进入到call_class_loads内部
static void call_class_loads(void)
{
int i;
// Detach current loadable list.
struct loadable_class *classes = loadable_classes;
int used = loadable_classes_used;
loadable_classes = nil;
loadable_classes_allocated = 0;
loadable_classes_used = 0;
// Call all +loads for the detached list.
for (i = 0; i < used; i++) {
Class cls = classes[i].cls;
load_method_t load_method = (load_method_t)classes[i].method;
if (!cls) continue;
if (PrintLoading) {
_objc_inform("LOAD: +[%s load]\n", cls->nameForLogging());
}
(*load_method)(cls, SEL_load);
}
// Destroy the detached list.
if (classes) free(classes);
}
复制代码
能够找到(*load_method)(cls, SEL_load);该函数，该函数是直接使用IMP执行的，IMP就是函数地址，能够直接访问函数而不用消息的转发流程。
+initialize调用
- +initialize方法会在类第一次接收到消息时调用
- 先调用父类的+initialize，再调用子类的+initialize
- 先初始化父类，再初始化子类，每一个类只会初始化1次
objc源码解读过程objc-msg-arm64.x->objc_msgSend->objc->runtime-new->class_getinstanceMethod->lookUpImpOrNil->lookUpImpOrForward->_clas_initialize->callInitialize->objc_msgSend(cls,SEL_Initialize) 在runtime-new.h4819行
Method class_getInstanceMethod(Class cls, SEL sel)
{
if (!cls || !sel) return nil;
// This deliberately avoids +initialize because it historically did so.
// This implementation is a bit weird because it's the only place that // wants a Method instead of an IMP. #warning fixme build and search caches // Search method lists, try method resolver, etc. lookUpImpOrNil(cls, sel, nil, NO/*initialize*/, NO/*cache*/, YES/*resolver*/); #warning fixme build and search caches return _class_getMethod(cls, sel); } 复制代码
根据lookUpImpOrNil查看4916行
IMP lookUpImpOrForward(Class cls, SEL sel, id inst,
bool initialize, bool cache, bool resolver)
{
IMP imp = nil;
bool triedResolver = NO;
runtimeLock.assertUnlocked();
// Optimistic cache lookup
if (cache) {
imp = cache_getImp(cls, sel);
if (imp) return imp;
}
// runtimeLock is held during isRealized and isInitialized checking
// to prevent races against concurrent realization.
// runtimeLock is held during method search to make
// method-lookup + cache-fill atomic with respect to method addition.
// Otherwise, a category could be added but ignored indefinitely because
// the cache was re-filled with the old value after the cache flush on
// behalf of the category.
runtimeLock.lock();
checkIsKnownClass(cls);
if (!cls->isRealized()) {
realizeClass(cls);
}
if (initialize && !cls->isInitialized()) {
runtimeLock.unlock();
_class_initialize (_class_getNonMetaClass(cls, inst));
runtimeLock.lock();
//当第一次收到消息，cls没有初始化，则调用_class_initialize进行初始化
}
retry:
runtimeLock.assertLocked();
// Try this class's cache. imp = cache_getImp(cls, sel); if (imp) goto done; // Try this class's method lists.
//在本类中查找method
{
Method meth = getMethodNoSuper_nolock(cls, sel);
if (meth) {
log_and_fill_cache(cls, meth->imp, sel, inst, cls);
imp = meth->imp;
goto done;
}
}
// Try superclass caches and method lists.
{
unsigned attempts = unreasonableClassCount();
for (Class curClass = cls->superclass;
curClass != nil;
curClass = curClass->superclass)
{
// Halt if there is a cycle in the superclass chain.
if (--attempts == 0) {
_objc_fatal("Memory corruption in class list.");
}
// Superclass cache.
imp = cache_getImp(curClass, sel);
if (imp) {
if (imp != (IMP)_objc_msgForward_impcache) {
// Found the method in a superclass. Cache it in this class.
log_and_fill_cache(cls, imp, sel, inst, curClass);
goto done;
}
else {
// Found a forward:: entry in a superclass.
// Stop searching, but don't cache yet; call method // resolver for this class first. break; } } // Superclass method list. Method meth = getMethodNoSuper_nolock(curClass, sel); if (meth) { log_and_fill_cache(cls, meth->imp, sel, inst, curClass); imp = meth->imp; goto done; } } } // No implementation found. Try method resolver once. if (resolver && !triedResolver) { runtimeLock.unlock(); _class_resolveMethod(cls, sel, inst); runtimeLock.lock(); // Don't cache the result; we don't hold the lock so it may have // changed already. Re-do the search from scratch instead. triedResolver = YES; goto retry; } // No implementation found, and method resolver didn't help.
// Use forwarding.
imp = (IMP)_objc_msgForward_impcache;
cache_fill(cls, sel, imp, inst);
done:
runtimeLock.unlock();
return imp;
}
复制代码
当第一次收到消息，cls没有初始化，则调用_class_initialize进行初始化 咱们进入到_class_initialize内部objc-initialize.mm484行
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!"); } } 复制代码
能够看出来，和+load方法同样，先父类后子类。而后赋值reallyInitialize = YES;，后边使用try主动调用callInitialize(cls);，来到callInitialize(cls);内部：
void callInitialize(Class cls)
{
((void(*)(Class, SEL))objc_msgSend)(cls, SEL_initialize);
asm("");
}
复制代码
能够看到最终仍是使用((void(*)(Class, SEL))objc_msgSend)(cls, SEL_initialize)主动调用了该函数。
区别
+initialize和+load的很大区别是，+initialize是经过objc_msgSend进行调用的，因此有如下特色 若是子类没有实现+initialize，会调用父类的+initialize（因此父类的+initialize可能会被调用屡次） 若是分类实现了+initialize，就覆盖类自己的+initialize调用
用伪代码实现如下思路：
if(class 没有初始化){
父类初始化
子类初始化
调用initialize
}
若是子类没有实现initialize，则去调用父类initialize。
复制代码
至于子类没有实现的话是直接调用父类的initialize，是使用objc-msgsend的缘由。
验证
@interface FYPerson : NSObject
@end
+(void)initialize{
printf("\n%s",__func__);
}
+(void)load{
printf("\n%s",__func__);
}
@interface FYPerson (test1)
@end
+(void)initialize{
printf("\n%s",__func__);
}
+(void)load{
printf("\n%s",__func__);
}
//输出
+[FYPerson load]
+[FYPerson(test2) load]
+[FYPerson(test1) load]
复制代码
总结
+load是根据函数地址直接调用，initialize是经过objc_msgSend调用+load是runtime加载类、分类时候调用（只会调用一次）initialize是第一次接受消息的时候调用，每一个类只会调用一次（子类没实现，父类可能被调用屡次）+load调用优先于initialize,子类调用+load以前会调用父类的+load，再调用分类的+load,分类之间先编译，先调用。initialize先初始化父类，再初始化子类（可能最终调用父类的initialize）
关联对象本质
关联对象的本质-结构体
继承NSObject是能够能够直接使用@property (nonatomic,assign) int age;，可是在Category中会报错，那么怎么实现和继承基类同样的效果呢？ 咱们查看Category结构体
struct _category_t {
const char *name; //"FYPerson"
struct _class_t *cls;
const struct _method_list_t *instance_methods;
const struct _method_list_t *class_methods;
const struct _protocol_list_t *protocols;
const struct _prop_list_t *properties;
};
复制代码
其中const struct _prop_list_t *properties;是存储属性的，可是缺乏成员变量，而咱们也不能主动在_category_t插入ivar，那么咱们可使用objc_setAssociatedObject将属性的值存储全局的AssociationsHashMap中，使用的时候objc_getAssociatedObject(id object, const void *key),不使用的时候删除使用objc_removeAssociatedObjects删除。
咱们进入到objc_setAssociatedObject内部,objc-references.mm275行
void _object_set_associative_reference(id object, void *key, id value, uintptr_t policy) {
// retain the new value (if any) outside the lock.
ObjcAssociation old_association(0, nil);
//根据key value 处理
id new_value = value ? acquireValue(value, policy) : nil;
{
AssociationsManager manager;
//生成一个全局的 HashMap
AssociationsHashMap &associations(manager.associations());
disguised_ptr_t disguised_object = DISGUISE(object);
//有value 就处理
if (new_value) {
// break any existing association.
// 遍历 hashMap是否有该obj
AssociationsHashMap::iterator i = associations.find(disguised_object);
if (i != associations.end()) {
// secondary table exists
//有的话 更新其 value
ObjectAssociationMap *refs = i->second;
ObjectAssociationMap::iterator j = refs->find(key);
if (j != refs->end()) {
old_association = j->second;
j->second = ObjcAssociation(policy, new_value);
} else {
(*refs)[key] = ObjcAssociation(policy, new_value);
}
} else {
// create the new association (first time).
//没有的话 赋值给 refs
ObjectAssociationMap *refs = new ObjectAssociationMap;
associations[disguised_object] = refs;
(*refs)[key] = ObjcAssociation(policy, new_value);
object->setHasAssociatedObjects();
}
} else {
// setting the association to nil breaks the association.
AssociationsHashMap::iterator i = associations.find(disguised_object);
if (i != associations.end()) {
ObjectAssociationMap *refs = i->second;
ObjectAssociationMap::iterator j = refs->find(key);
if (j != refs->end()) {
old_association = j->second;
//删除refs
refs->erase(j);
}
}
}
}
// release the old value (outside of the lock).
if (old_association.hasValue()) ReleaseValue()(old_association);
}
复制代码
经过该函数咱们了解到
- 关联对象并非存储在关联对象的自己内存中
- 关联对象是存储在全局统一的
AssociationsManager管理的AssociationsHashMap中 - 传入value =nil，会移除该关联对线
AssociationsManager实际上是管理了已key为id object对应的AssociationsHashMap，AssociationsHashMap存储了key对应的ObjcAssociation，ObjcAssociation是存储了value和policy，ObjcAssociation的数据结构以下：
class ObjcAssociation {
uintptr_t _policy;
id _value;
*****
}
复制代码
具体抽象关系见下图
AssociationsManager --> AssociationsHashMap --> ObjectAssociationMap
-->void * ObjectAssociation -->uintprt_t _policy ,id _value;
复制代码
简单来说就是一个全局变量保存了以class为key对应的AssociationsHashMap，这个AssociationsHashMap存储了一个key对应的ObjectAssociation，ObjectAssociation包含了value和_policy。经过2层map保存了数据。
关联对象的使用
| objc_setAssociatedObject | obj,key,value,policy |
|---|---|
| objc_getAssociatedObject | 根据 obj 和 key获取值 |
| void objc_removeAssociatedObjects(id object) | 根据obj 删除关联函数 |
objc_AssociationPolicy的类型：
| OBJC_ASSOCIATION_ASSIGN | weak 引用 |
|---|---|
| OBJC_ASSOCIATION_RETAIN_NONATOMIC | 非原子强引用 |
| OBJC_ASSOCIATION_COPY_NONATOMIC | 非原子至关于copy |
| OBJC_ASSOCIATION_RETAIN | 强引用 |
| OBJC_ASSOCIATION_COPY | 原子操做，至关于copy |
代码示例
@interface NSObject (test)
@property (nonatomic,assign) NSString * name;
@end
#import "NSObject+test.h"
#import "objc/runtime.h"
@implementation NSObject (test)
-(void)setName:(NSString *)name{
objc_setAssociatedObject(self, @selector(name), name, OBJC_ASSOCIATION_COPY);
}
- (NSString *)name{
return objc_getAssociatedObject(self, @selector(name));
}
@end
NSObject *obj =[[NSObject alloc]init];
obj.name = @"老弟来了";
printf("%s",obj.name.UTF8String);
//老弟来了
复制代码
这段代码咱们实现了给基类添加一个成员变量name，而后又成功取出了值，标示咱们作新增的保存成员变量的值是对的。
总结
- Category
+load在冷启动时候执行，执行顺序和编译顺序成弱相关，先父类，后子类，并且每一个类执行一次，执行是直接调用函数地址。 - Category
+initialize在第一次接受消息执行，先父类，后子类，子类没实现，会调用父类，利用objc-msgsend机制调用。 - Category 能够利用
Associative添加和读取属性的值
资料下载
-
本文章之因此图片比较少，我以为仍是跟着代码敲一遍，印象比较深入。
最怕一辈子碌碌无为，还安慰本身平凡难得。
广告时间
相关文章
- 1. iOS底层原理之`OC语法`(Category、load、initialize、关联对象)
- 2. iOS底层原理探索 — isa原理与对象的本质
- 3. 底层原理（一）对象的本质
- 4. iOS底层原理总结 - 关联对象实现原理
- 5. iOS底层原理总结 - Category的本质
- 6. iOS底层原理总结--OC对象的本质(二)
- 7. iOS底层原理总结 - 探寻OC对象的本质
- 8. iOS底层原理总结--OC对象的本质(一)
- 9. iOS底层原理 - OC对象的本质（一）
- 10. IOS 底层原理 对象的本质--(1)
- 更多相关文章...
- • 一对一关联查询 - MyBatis教程
- • 一对多关联查询 - MyBatis教程
- • Java Agent入门实战（三）-JVM Attach原理与使用
- • Docker容器实战(八) - 漫谈 Kubernetes 的本质
相关标签/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
最新文章
- 1. python的安装和Hello，World编写
- 2. 重磅解读：K8s Cluster Autoscaler模块及对应华为云插件Deep Dive
- 3. 鸿蒙学习笔记2（永不断更）
- 4. static关键字 和构造代码块
- 5. JVM笔记
- 6. 无法启动 C/C++ 语言服务器。IntelliSense 功能将被禁用。错误: Missing binary at c:\Users\MSI-NB\.vscode\extensions\ms-vsc
- 7. 【Hive】Hive返回码状态含义
- 8. Java树形结构递归（以时间换空间）和非递归（以空间换时间）
- 9. 数据预处理---缺失值
- 10. 都要2021年了，现代C++有什么值得我们学习的？
欢迎关注本站公众号,获取更多信息
