Lines Matching full:variable
35 also contain various variable bindings to automatic (stack) or managed
50 Block Variable Declarations
53 A :block-term:`variable with Block type` is declared using function
55 valid Block variable declarations:
160 The compiler is not required to capture a variable if it can prove
161 that no references to the variable will actually be evaluated.
162 Programmers can force a variable to be captured by referencing it in a
169 This matters when capturing the variable has side-effects, as it can
174 the local scope of the Block. Such variable declarations should be
231 is automatically recovered after last use of said variable. An
237 In the case where a ``__block`` variable is a Block one must assume
238 that the ``__block`` variable resides in allocated storage and as such
244 trying to update the shared variable and the need for synchronization
262 that also of id. A variable or expression of Block type may be
296 In garbage collected environments, the ``__weak`` variable is set to
298 ``__block`` variable resides in the heap (either by default or via
316 object. Note that this does not change the type of a variable of
339 cases, they are copied as if the variable were const-qualified, and
354 stack-based version is called at the variable's normal end of scope.
358 normal variable of C pointer type.
