Lines Matching refs:retain
26 When Apple's garbage collector is enabled, the usual [obj retain] and [obj release] messages
32 GC mode to forcibly retain the object. In Retain/Release (RR) mode the CFRetain function has
33 the same effect as [obj retain]. Note that GC vs. RR is selected at runtime.
37 receiving an Objective-C object from an alloc or copy method take care that you must retain
51 Consider the effect on the retain count from each statement (alloc, CFRetain, release)
64 return [r retain];
81 the wxGCSafeRelease call becomes critical as it releases the retain from the first time
117 [NSObject -alloc]'ed and thus does not need a retain
129 @abstract Simply does [p retain].
149 released by managing the reference count using the retain/release semantics. In GC-mode
160 // NOTE: this is from alloc. Do NOT retain
164 // non-GC: Simply realizes it's an Objective-C object and calls [p retain]
167 // GC: Objective-C retain/release mean nothing in GC mode
168 // non-GC: This is a normal release call, balancing the retain
172 // non-GC: Retain count is the same as it was (retain then release)
206 A pointer holder that does retain its argument.
207 NOTE: It is suggest that you instead use wxObjcAutoRefFromAlloc<T> foo([aRawPointer retain])
215 Uses the underlying wxObjcAutoRefFromAlloc and simply does a typical [p retain] such that
216 in RR-mode the object is in effectively the same retain-count state as it would have been
222 // In RR mode it does retain and the superclass does retain/release thus resulting in an overall retain.