来自块语言规范:

In addition to the new Block type we also introduce a new storage qualifier, __block, for local variables. [testme: a __block declaration within a block literal] The __block storage qualifier is mutually exclusive to the existing local storage qualifiers auto, register, and static.[testme] Variables qualified by __block act as if they were in allocated storage and this storage is automatically recovered after last use of said variable. An implementation may choose an optimization where the storage is initially automatic and only "moved" to allocated (heap) storage upon a Block_copy of a referencing Block. Such variables may be mutated as normal variables are. In the case where a __block variable is a Block one must assume that the __block variable resides in allocated storage and as such is assumed to reference a Block that is also in allocated storage (that it is the result of a Block_copy operation). Despite this there is no provision to do a Block_copy or a Block_release if an implementation provides initial automatic storage for Blocks. This is due to the inherent race condition of potentially several threads trying to update the shared variable and the need for synchronization around disposing of older values and copying new ones. Such synchronization is beyond the scope of this language specification.

有关__block变量应该编译为什么的详细信息，请参见块实现规范，第2.3节。

希望这对你有所帮助

让我们假设我们有这样一个代码:

{
     int stackVariable = 1;

     blockName = ^()
     {
      stackVariable++;
     }
}

它会给出一个类似“变量不可赋值”的错误，因为块内的堆栈变量默认是不可变的。

在它的声明之前添加__block(存储修饰符)，使它在块内部是可变的，即__block int stackVariable=1;

来自块语言规范:

In addition to the new Block type we also introduce a new storage qualifier, __block, for local variables. [testme: a __block declaration within a block literal] The __block storage qualifier is mutually exclusive to the existing local storage qualifiers auto, register, and static.[testme] Variables qualified by __block act as if they were in allocated storage and this storage is automatically recovered after last use of said variable. An implementation may choose an optimization where the storage is initially automatic and only "moved" to allocated (heap) storage upon a Block_copy of a referencing Block. Such variables may be mutated as normal variables are. In the case where a __block variable is a Block one must assume that the __block variable resides in allocated storage and as such is assumed to reference a Block that is also in allocated storage (that it is the result of a Block_copy operation). Despite this there is no provision to do a Block_copy or a Block_release if an implementation provides initial automatic storage for Blocks. This is due to the inherent race condition of potentially several threads trying to update the shared variable and the need for synchronization around disposing of older values and copying new ones. Such synchronization is beyond the scope of this language specification.

有关__block变量应该编译为什么的详细信息，请参见块实现规范，第2.3节。

这意味着它作为前缀的变量可以在块中使用。

__block是一个存储限定符，可以以两种方式使用:

标记变量位于原始变量的词法作用域和在该作用域中声明的任何块之间共享的存储中。clang将生成一个表示该变量的结构体，并通过引用(而不是值)使用该结构体。 在MRC中，__block可用于避免保留块捕获的对象变量。注意这对ARC不起作用。在ARC中，你应该使用__weak。

你可以参考苹果文档的详细信息。

__block是一种存储类型，用于使作用域变量可变，更坦率地说，如果你声明一个变量与此说明符，它的引用将被传递给块而不是只读副本，详情请参阅iOS中的块编程