Lines Matching refs:variables

152 functions and global variables as one would expect, as well as static
153 local variables. [testme]
155 Local automatic (stack) variables referenced within the compound
172 The lifetime of variables declared in a Block is that of a function;
173 each activation frame contains a new copy of variables declared within
179 (nest) and all variables captured by any nested blocks are implicitly
183 Block variables at global or local static scope.
226 qualifier, :block-term:`__block`, for local variables. [testme: a
234 a Block_copy of a referencing Block.  Such variables may be mutated as
235 normal variables are.
275 references to instance variables are also imported into the lexical
276 scope of the compound statement. These variables are implicitly
278 copy. The net effect is that instance variables can be mutated.
281 variables of automatic storage referenced within the Block expression
283 Object variables of ``__block`` storage type are assumed to hold
290 ``__weak`` specifier for ``__block`` variables of object type.  If
292 variables to be kept without retain messages being sent. This
300 start ``__block`` variables on the stack and migrate them to the heap
305 ``__weak`` ``__block`` variables.
314 As usual, within the block, references to captured variables become
327 A Block that referenced these variables would import the variables as
336 Captured variables are copied into the Block at the instant of
342 Captured variables in Blocks on the stack are destroyed when control
344 expression.  Captured variables in Blocks on the heap are destroyed
350 from the stack, ``__block`` variables are copied using their normal
352 variables are copied as x-values if that is possible, then as l-values
360 Member variables that are Blocks may not be overloaded by the types of