Runtime精进
一、什么是runtime
runtime是一套用C语言和汇编写的一套API,存在意义是支持OC动态性,将一些工作编译连接推迟到运行时,只有编译器是不够的,还需要一个运行时系统,这就是runtime机制。其中最主要的就是消息机制。 消息转发和消息传递。
使用场景
注意事项
- swizzling应该总在+load中执行
- swizzling应该总是在dispatch_once中执行
- +load中调用的时候,不要调用[super load]多次调用,会出现无效的假象
- 避免swizzling代码被重复执行,可以通过GCD的dipatch_once函数来解决,利用dispatch_once函数内代码只会执行一次的特性。
1.UI控件防止短时间内重复点击
实现思路: 1.动态添加两个属性,添加对应set,get方法 根据情况判断定条件
2. 是否ignore
3. 间隔时间
#import "UIControl+Limit.h"
#import <objc/runtime.h>
// 设置控件不能连续点击间隔
// 熟悉使用的相关控件
static const char *UIControl_acceptEventInternal = "UIControl_acceptEventInternal";
static const char *UIControl_ignoreEvent = "UIControl_ignoreEvent";
@implementation UIControl (Limit)
#pragma mark - acceptEventInternal
//动态添加类型
// set方法
- (void)setAcceptEventInterval:(NSTimeInterval)acceptEventInterval {
// 动态设置新属性
objc_setAssociatedObject(self, UIControl_acceptEventInternal, @(acceptEventInterval), OBJC_ASSOCIATION_RETAIN_NONATOMIC);
}
//get方法
- (NSTimeInterval)acceptEventInterval {
return [objc_getAssociatedObject(self, UIControl_acceptEventInternal) doubleValue];
}
#pragma mark -ignoreEvent
- (void)setIgnoreEvent:(NSTimeInterval)ignoreEvent {
objc_setAssociatedObject(self, UIControl_ignoreEvent, @(ignoreEvent), OBJC_ASSOCIATION_ASSIGN);
}
- (NSTimeInterval)ignoreEvent {
return [objc_getAssociatedObject(self, UIControl_ignoreEvent) boolValue];
}
#pragma mark - Swizzling
+ (void)load {
Method a = class_getInstanceMethod(self, @selector(sendAction:to:forEvent:));
Method b = class_getInstanceMethod(self, @selector(swizzled_sendAction:to:forEvent:));
method_exchangeImplementations(a, b); // 交换方法
}
- (void)swizzled_sendAction:(SEL)action to:(id)target forEvent:(UIEvent *)event {
if (self.ignoreEvent) { // 忽略事件
NSLog(@"btnAction is intercepted");
return;
}
if (self.acceptEventInterval >0) {
self.ignoreEvent = YES;
[self performSelector:@selector(setIgnoreEventWithNo) withObject:nil afterDelay:self.acceptEventInterval];
}
[self swizzled_sendAction:action to:target forEvent:event];
}
- (void)setIgnoreEventWithNo {
self.ignoreEvent = NO;
}
@end
2.防止数组越界
NSNumber,NSArray,NSDictionary这些类族无效。
#import "NSArray+CrashHandle.h"
#import <objc/runtime.h>
//使用runtime解决数组越界问题
// 1.对应d类族 替换到真身对应方法
@implementation NSArray (CrashHandle)
+ (void)load {
//交换系统方法
Method fromMethod = class_getInstanceMethod(objc_getClass("__NSArrayI"), @selector(objectAtIndex:));
Method toMethod = class_getInstanceMethod(objc_getClass("__NSArrayI"), @selector(cm_objectAtIndex:));
method_exchangeImplementations(fromMethod, toMethod);
}
-(id)cm_objectAtIndex:(NSUInteger)index {
if (self.count -1 < index) {
//数组越界
@try {
return [self cm_objectAtIndex:index];
} @catch (NSException *exception) {
//崩溃后打印崩溃信息,如果线上,这里将崩溃信息发送到服务器
NSLog(@"----------%s Crash Because Method %s---------\n", class_getName(self.class), __func__);
// NSLog(@"%@"m [exception callStack])
return nil;
} @finally {
}
} else {
return [self cm_objectAtIndex:index];
}
}
@end
3. 统计VC加载次数
load类方法是程序运行时这个类被加载到内存中就调用的一个方法,执行比较早,不需要我们手动调用。
#import "UIViewController+Logging.h"
#import <objc/runtime.h>
@implementation UIViewController (Logging)
//类加载的时候会被执行
+(void)load {
swizzleMehod([self class], @selector(viewDidAppear:), @selector(swizzle_viewDidAppear:));
}
// 交换方法
- (void)swizzle_viewDidAppear:(BOOL)animated {
[self swizzle_viewDidAppear:animated];
//Logging
NSLog(@" - %@",NSStringFromClass([self class])); //打印当前类型名称
}
//交换方法
void swizzleMehod(Class class, SEL originalSelector, SEL swizzledSelector) {
Method originalMethod = class_getInstanceMethod(class, originalSelector);
Method swizzledMethod = class_getInstanceMethod(class, swizzledSelector);
BOOL didAddMethod = class_addMethod(class, originalSelector, method_getImplementation(swizzledMethod), method_getTypeEncoding(swizzledMethod));
if(didAddMethod) {
class_replaceMethod(class, swizzledSelector, method_getImplementation(originalMethod), method_getTypeEncoding(originalMethod));
} else {
method_exchangeImplementations(originalMethod, swizzledMethod);
}
}
@end
用法一:交换类的方法
实现load类方法 — 类加载运行的时候就会调用
消息传递
掌握对应的数据结构 OC函数调用都会转化成objc_msgSend(id self, SEL op, …)函数
查看几个对应结构体熟悉概念
类对象(objc_class):单例,在编译期产生用于创建实例对象
类实例(objc_object)
元类(Meta Class)
Mehod (objc_method)
SEL (objc_selector)
IMP
类缓存 (objc_cache)
Category (objc_category)
//对象
struct objc_object {
Class isa OBJC_ISA_AVAILABILITY;
};
//类
struct objc_class {
Class isa OBJC_ISA_AVAILABILITY;
#if !__OBJC2__
Class super_class OBJC2_UNAVAILABLE;
const char *name OBJC2_UNAVAILABLE;
long version OBJC2_UNAVAILABLE;
long info OBJC2_UNAVAILABLE;
long instance_size OBJC2_UNAVAILABLE;
struct objc_ivar_list *ivars OBJC2_UNAVAILABLE;
struct objc_method_list **methodLists OBJC2_UNAVAILABLE;
struct objc_cache *cache OBJC2_UNAVAILABLE;
struct objc_protocol_list *protocols OBJC2_UNAVAILABLE;
#endif
} OBJC2_UNAVAILABLE;
//方法列表
struct objc_method_list {
struct objc_method_list *obsolete OBJC2_UNAVAILABLE;
int method_count OBJC2_UNAVAILABLE;
#ifdef __LP64__
int space OBJC2_UNAVAILABLE;
#endif
/* variable length structure */
struct objc_method method_list[1] OBJC2_UNAVAILABLE;
} OBJC2_UNAVAILABLE;
//方法
struct objc_method {
SEL method_name OBJC2_UNAVAILABLE;
char *method_types OBJC2_UNAVAILABLE;
IMP method_imp OBJC2_UNAVAILABLE;
}
几个步骤:
- 系统先找到消息的接受对象,通过对象的isa 找到它的类
- 类中查找method_list,是否有selector方法
- 没有查找父类的method_list
- 找到对应的method,执行它的IMP
- 转发IMP的return 值
消息转发
消息转发失败反复会执行doesNotRecognizeSelector: 方法报unregnized selector
完整的转发流程: resolveInstance forwardTarget forwardInvacation
#import "ViewController.h"
#import "objc/runtime.h"
@interface Person: NSObject
@end
@implementation Person
- (void)foo {
NSLog(@"Doing foo");//Person的foo函数
}
@end
@interface ViewController ()
@end
@implementation ViewController
- (void)viewDidLoad {
[super viewDidLoad];
// Do any additional setup after loading the view, typically from a nib.
//执行foo函数
[self performSelector:@selector(foo)];
}
+ (BOOL)resolveInstanceMethod:(SEL)sel {
return YES;//返回YES,进入下一步转发
}
- (id)forwardingTargetForSelector:(SEL)aSelector {
return nil;//返回nil,进入下一步转发
}
- (NSMethodSignature *)methodSignatureForSelector:(SEL)aSelector {
if ([NSStringFromSelector(aSelector) isEqualToString:@"foo"]) {
return [NSMethodSignature signatureWithObjCTypes:"v@:"];//签名,进入forwardInvocation
}
return [super methodSignatureForSelector:aSelector];
}
- (void)forwardInvocation:(NSInvocation *)anInvocation {
SEL sel = anInvocation.selector;
Person *p = [Person new];
if([p respondsToSelector:sel]) {
[anInvocation invokeWithTarget:p];
}
else {
[self doesNotRecognizeSelector:sel];
}
}
@end
runtime应用
大型框架的利器,应用场景
- 关联对象
- 方法魔法
- 消息转发热更解决bug
- 实现NScoding的自动归档和自动接档
- 实现字典和模型的自动转换
1.关联对象
相关API
void objc_setAssociatedObject(id object, const void *key, id value, objc_AssociationPolicy policy) //获取关联的对象 id objc_getAssociatedObject(id object, const void *key) //移除关联的对象 void objc_removeAssociatedObjects(id object)
demo展示
@interface UIView (DefaultColor)
@property (nonatomic, strong) UIColor *defaultColor;
@end
@implementation UIView (DefaultColor)
@dynamic defaultColor;
static char kDefaultColorKey;
- (void)setDefaultColor:(UIColor *)defaultColor {
objc_setAssociatedObject(self, &kDefaultColorKey, defaultColor, OBJC_ASSOCIATION_RETAIN_NONATOMIC);
}
- (id)defaultColor {
return objc_getAssociatedObject(self, &kDefaultColorKey);
}
@end
2.方法魔法
class_addMethod([self class], sel, (IMP)fooMethod, "v@:");`
-
cls 被添加方法的类
-
name 添加的方法的名称的SEL
-
imp 方法的实现。该函数必须至少要有两个参数,self,_cmd
类型编码 -
方法交换
+ (void)load {
//原子操作确保在不同的线程中代码只执行了一次。 dispatch_once满足了需求 swizzleing 改变了全局的转台,确保每个预防措施在运行时都是可用的。
static dispatch_once_t onceToken;
dispatch_once(&onceToken, ^{
Class class = [self class];
SEL originalSelector = @selector(viewDidLoad);
SEL swizzledSelector = @selector(jkviewDidLoad);
Method originalMethod = class_getInstanceMethod(class, originalSelector);
Method swizzledMethod = class_getInstanceMethod(class, swizzledSelector);
BOOL didAddMethod = class_addMethod(class, originalSelector, method_getImplementation(swizzledMethod), method_getTypeEncoding(swizzledMethod));
if (didAddMethod) {//添加成成功
class_replaceMethod(class, swizzledSelector, method_getImplementation(originalMethod), method_getTypeEncoding(originalMethod));
} else {
method_exchangeImplementations(originalMethod, swizzledMethod); //交换两个方法
}
});
}
- (void)jkviewDidLoad {
NSLog(@"替换的方法");
[self jkviewDidLoad];
}
swizzling 应该只在+load(一个类被初始装载时调用)中完成,+initialize 是在应用调用该类的类方法或实例方法前调用的,在Objective-c 的运行时中,
KVO实现
1.Apple使用了isa-swizzling 来实现KVO,动态机制创建一个新的名为:NSKVONotifying_A的新类
NSCoding 使用
数据写到硬盘上的时候,将数据序列化然后转化为二进制文件从而便于在磁盘上读写。读取的时候进行反序列化。
//实现NSCoding的自动归档和自动接档
- (id)initWithCoder:(NSCoder *)aDecoder {
if (self = [super init]) {
unsigned int outCount;
Ivar *ivars = class_copyIvarList([self class], &outCount); // 获取对象属性列表
for (int i = 0; i< outCount; ++i) {
Ivar ivar = ivars[i];
NSString *key = [NSString stringWithUTF8String:ivar_getName(ivar)]; //得到属性utf8字符串编码
[self setValue:[aDecoder decodeObjectForKey:key] forKey:key];
}
}
return self;
}
- (void)encodeWithCoder:(NSCoder *)aCoder {
unsigned int outCount;
Ivar *ivars = class_copyIvarList([self class], &outCount);
for (int i = 0; i< outCount; ++i) {
Ivar ivar = ivars[i];
NSString * key = [NSString stringWithUTF8String:ivar_getName(ivar)];
[aCoder encodeObject:[self valueForKey:key] forKey:key];
}
}
实现字典和模型的自动转换
// 字典和模型的自动转换(MJExtension)
// 实现原理:用runtime提供的函数遍历modeld自身所有属性,如果属性在jsonz中存在,则将其赋值
// 熟悉使用到相关函数 s熟悉对应提供的API接口 熟悉对应英文
- (instancetype)initWithDict:(NSDictionary *)dict {
if (self = [super init]) {
// 获取类的属性及属性对应的类型
NSMutableArray *keys = [NSMutableArray array];
NSMutableArray *attributes = [NSMutableArray array];
unsigned int outCount;
objc_property_t *properties = class_copyPropertyList([self class], &outCount);
for (int i = 0; i< outCount; ++i) {
objc_property_t property = properties[i];
// 通过property_getName 函数获取属性的名字
NSString *propertyName = [NSString stringWithCString:property_getName(property) encoding:NSUTF8StringEncoding];
[keys addObject:propertyName];
// 通过propety_getAttribute函数获取属性的名字和@encode编码
NSString *propertyAttribute = [NSString stringWithCString:property_getAttributes(property) encoding:NSUTF8StringEncoding];
[attributes addObject:propertyAttribute];
}
// 立即释放properties指向的内存
free(properties);
// 根据类型给属性赋值
for (NSString *key in keys) {
if ([dict valueForKey:key] == nil) continue;
// dict包含对应字段
[self setValue:[dict valueForKey:key] forKey:key];
}
}
return self;
}
怎样会站在作者的角度得出同样的结论?
提升点
- 熟悉对应头文件API 熟悉对应文档
关键点: 消息传递 消息转发 对应应用
大家的总结似乎都是一样
很多作者写的内容看起来 逻辑很不经推敲,没有一个比较完善的思维模型,大部分都是抄袭来的,很多知识都帮助不了读者建立一个连贯的理解或者是树状发散效果,只是更多知识的堆砌。