影视网站代理,wordpress防御ip攻击,广东东莞有哪些厂招工信息,杭州网站设计开发应当使用#xff1a;property (nonatomic, copy)今天在这个问题上犯错误了#xff0c;找了好久才知道原因。另外#xff0c;简单的进行反汇编看了下#xff0c;Block 被存储在静态变量区#xff0c;运行时构造出一个运行栈#xff0c;进行调用。retain 并不会改变 Block … 应当使用property (nonatomic, copy)今天在这个问题上犯错误了找了好久才知道原因。另外简单的进行反汇编看了下Block 被存储在静态变量区运行时构造出一个运行栈进行调用。retain 并不会改变 Block 的引用计数因此对 Block 应用 retain 相当于 assign。但是既然在静态存储区为什么会出现 EXC_BAD_ACCESS 呢代码都在的呀。网上都说 Block 在栈上这应该是错误的指向 Block 代码的指针在栈上。我感觉原因是这样 执行静态区的代码需要特殊的构造比如加载到寄存器调整好 ESP 等。 而堆上的代码可以直接执行。期待更详细的解释。When storing blocks in properties, arrays or other data structures, there’s an important difference between using copy or retain. And in short, you should always use copy.When blocks are first created, they are allocated on the stack. If the block is called when that stack frame has disappeared, it can have disastrous consequences, usually a EXC_BAD_ACCESS or something plain weird.If you retain a stack allocated block (as they all start out being), nothing happens. It continues to be stack allocated and will crash your app when called. However, if you copy a stack allocated block, it will copy it to the heap, retaining references to local and instance variables used in the block, and calling it will behave as expected. However, if you copy a heap allocated block, it doesn’t copy it again, it just retains it.So you should always declare your blocks as properties like this:property (copy, ...) (int)(^aBlock)();
And never like this:property (retain, ...) (int)(^aBlock)();
And when providing blocks to NSMutableArrays and the like, always copy, never retain.转载于:https://www.cnblogs.com/Proteas/archive/2012/06/26/2563747.html
