Lines Matching refs:as

65 An empty parameter list does not represent, as K&R provide, an
67 as a convenience.
78 Block. It is introduced by the use of the ``^`` token as a unary
88 where type expression is extended to allow ``^`` as a Block reference
89 (pointer) where ``*`` is allowed as a function reference (pointer).
123 reference declarations as it accommodates function pointer
140 are equivalent expressions, as is:
152 functions and global variables as one would expect, as well as static
156 statement of a Block are imported and captured by the Block as const
169 This matters when capturing the variable has side-effects, as it can
182 A Block literal expression may be used as the initialization value for
214 The copy operation ``Block_copy()`` is styled as a function that takes
216 type. The release operation, ``Block_release()``, is styled as a
230 ``__block`` act as if they were in allocated storage and this storage
234 a Block_copy of a referencing Block.  Such variables may be mutated as
238 that the ``__block`` variable resides in allocated storage and as such
263 messaged or used as a parameter wherever an id may be. The converse is
264 also true. Block references may thus appear as properties and are
277 qualified as references from self, and so self is imported as a const
297 nil when the object it references is collected, as long as the
301 only as a result of a ``Block_copy()`` operation.
315 const-qualified, as if they were references to members of a const
327 A Block that referenced these variables would import the variables as
339 cases, they are copied as if the variable were const-qualified, and
347 Variables declared as residing in ``__block`` storage may be initially
349 to the heap as a result of a ``Block_copy()`` operation. When copied
352 variables are copied as x-values if that is possible, then as l-values
356 References to ``this``, as well as references to non-static members of