block的原理是怎样的?本质是什么?
封装了函数调用以及调用环境的OC对象
__block的作用是什么?有什么使用注意点?
- __block可以用于解决block内部无法修改auto变量值的问题
- __block不能修饰全局变量、静态变量(static)
- 编译器会将__block变量包装成一个对象
- 使用注意点:在MRC情况下,当__block变量被copy到堆上时,不会对其产生强引用
block的属性修饰词为什么是copy?使用block有哪些使用注意?
block一旦没有进行copy操作,就不会在堆上,注意循环引用
block在修改NSMutableArray,需不需要添加__block?
不需要,在内部是指针访问
源码解读并分析
@interface Person : NSObject
@property (assign, nonatomic) int age;
@end
@implementation Person
@end
typedef void(^FGBlock)(void);
int main(int argc, const char * argv[]) {
@autoreleasepool {
Person *p = [[Person alloc] init];
p.age = 10;
__weak Person *weakP = p;
FGBlock block = ^{
NSLog(@"-----%d",weakP.age);
};
}
return 0;
}
我们写了个block和person对象,将他转成c++,在终端进入对应文件夹,输入,因为含__weak,所以和之前的转成c++代码有点区别
// 代码中含__weak
xcrun -sdk iphoneos clang -arch arm64 -rewrite-objc -fobjc-arc -fobjc-runtime=ios-8.0.0 main.m -o main.cpp
// 正常转换
xcrun -sdk iphoneos clang -arch arm64 -rewrite-objc main.m -o main.cpp
// 这是在c++代码里面看到的对应的片段
struct __block_impl {
void *isa;
int Flags;
int Reserved;
void *FuncPtr;
};
struct __main_block_impl_0 {
struct __block_impl impl;
struct __main_block_desc_0* Desc;
Person *__weak weakP;
__main_block_impl_0(void *fp, struct __main_block_desc_0 *desc, Person *__weak _weakP, int flags=0) : weakP(_weakP) {
impl.isa = &_NSConcreteStackBlock;
impl.Flags = flags;
impl.FuncPtr = fp;
Desc = desc;
}
};
static void __main_block_copy_0(struct __main_block_impl_0*dst, struct __main_block_impl_0*src) {_Block_object_assign((void*)&dst->weakP, (void*)src->weakP, 3/*BLOCK_FIELD_IS_OBJECT*/);}
static void __main_block_dispose_0(struct __main_block_impl_0*src) {_Block_object_dispose((void*)src->weakP, 3/*BLOCK_FIELD_IS_OBJECT*/);}
int main(int argc, const char * argv[]) {
{ __AtAutoreleasePool __autoreleasepool;
Person *p = objc_msgSend((objc_getClass("Person"), sel_registerName("alloc")), sel_registerName("init"));
objc_msgSend(p, sel_registerName("setAge:"), 10);
__attribute__((objc_ownership(weak))) Person *weakP = p;
FGBlock block = &__main_block_impl_0(__main_block_func_0, &__main_block_desc_0_DATA, weakP, 570425344));
}
return 0;
}
block本质上也是一个OC对象,它内部也有个isa指针, block是封装了函数调用以及函数调用环境的OC对象。
为了保证block内部能够正常访问外部的变量,block有个变量捕获机制
变量类型 | 捕获到block内部 | 访问方式 | |
局部变量 | auto | √ | 值传递 |
static | √ | 指针传递 | |
全局变量 | × | 直接访问 |
block有3种类型,可以通过调用class方法或者isa指针查看具体类型,最终都是继承自NSBlock类型
- __NSGlobalBlock__ ( _NSConcreteGlobalBlock )
- __NSStackBlock__ ( _NSConcreteStackBlock )
- __NSMallocBlock__ ( _NSConcreteMallocBlock )
block类型 | 环境 |
__NSGlobalBlock__ | 没有访问auto变量 |
__NSStackBlock__ | 访问了auto变量 |
__NSMallocBlock__ | __NSStackBlock__调用了copy |
在ARC环境下,编译器会根据情况自动将栈上的block复制到堆上,比如以下情况
- block作为函数返回值时
- 将block赋值给__strong指针时
- block作为Cocoa API中方法名含有usingBlock的方法参数时(例如数组的遍历 enumerateObjectsUsingBlock)
- block作为GCD API的方法参数时
对象类型的auto变量时
当block内部访问了对象类型的auto变量时,
如果block是在栈上
- 将不会对auto变量产生强引用;
如果block被拷贝到堆上
- 会调用block内部的copy函数
- copy函数内部会调用_Block_object_assign函数
- _Block_object_assign函数会根据auto变量的修饰符(__strong、__weak、__unsafe_unretained)做出相应的操作,形成强引用(retain)或者弱引用
如果block从堆上移除
- 会调用block内部的dispose函数
- dispose函数内部会调用_Block_object_dispose函数
- _Block_object_dispose函数会自动释放引用的auto变量(release)
__block修饰符
// 转换成c++前
typedef void(^FGBlock)(void);
int main(int argc, const char * argv[]) {
@autoreleasepool {
__block int age = 10;
FGBlock block = ^{
age = 20;
NSLog(@"-----%d",age);
};
}
return 0;
}
// 转换成c++后
typedef void(*FGBlock)(void);
struct __Block_byref_age_0 {
void *__isa;
__Block_byref_age_0 *__forwarding;
int __flags;
int __size;
int age;
};
struct __main_block_impl_0 {
struct __block_impl impl;
struct __main_block_desc_0* Desc;
__Block_byref_age_0 *age; // by ref
__main_block_impl_0(void *fp, struct __main_block_desc_0 *desc, __Block_byref_age_0 *_age, int flags=0) : age(_age->__forwarding) {
impl.isa = &_NSConcreteStackBlock;
impl.Flags = flags;
impl.FuncPtr = fp;
Desc = desc;
}
};
static void __main_block_func_0(struct __main_block_impl_0 *__cself) {
__Block_byref_age_0 *age = __cself->age; // bound by ref
(age->__forwarding->age) = 20;
NSLog((NSString *)&__NSConstantStringImpl__var_folders_1k_mt_kjd6155159xg6f3v0vgy80000gn_T_main_060428_mi_0,(age->__forwarding->age));
}
static void __main_block_copy_0(struct __main_block_impl_0*dst, struct __main_block_impl_0*src) {_Block_object_assign((void*)&dst->age, (void*)src->age, 8/*BLOCK_FIELD_IS_BYREF*/);}
static void __main_block_dispose_0(struct __main_block_impl_0*src) {_Block_object_dispose((void*)src->age, 8/*BLOCK_FIELD_IS_BYREF*/);}
static struct __main_block_desc_0 {
size_t reserved;
size_t Block_size;
void (*copy)(struct __main_block_impl_0*, struct __main_block_impl_0*);
void (*dispose)(struct __main_block_impl_0*);
} __main_block_desc_0_DATA = { 0, sizeof(struct __main_block_impl_0), __main_block_copy_0, __main_block_dispose_0};
int main(int argc, const char * argv[]) {
/* @autoreleasepool */ { __AtAutoreleasePool __autoreleasepool;
__attribute__((__blocks__(byref))) __Block_byref_age_0 age = {(void*)0,(__Block_byref_age_0 *)&age, 0, sizeof(__Block_byref_age_0), 10};
FGBlock block = ((void (*)())&__main_block_impl_0((void *)__main_block_func_0, &__main_block_desc_0_DATA, (__Block_byref_age_0 *)&age, 570425344));
}
return 0;
}
编译器会将__block变量包装成一个对象,用到时,通过结构体访问__forwarding指针再访问里面的age
__block的内存管理
当block在栈上时,并不会对__block变量产生强引用,
当block被copy到堆时
- 会调用block内部的copy函数
- copy函数内部会调用_Block_object_assign函数
- _Block_object_assign函数会对__block变量形成强引用(retain)