automatic-ref-counting

I use DLog macro in an ARC project, and I got the warning: Implicit declaration of function 'DLog' is invalid in C99 You can find DLog from http://iphoneincubator.com/blog/debugging/the-evolution-of-a-replacement-for-nslog How to fix this warning? I actually had this warning when calling Dlog without a capital L. I changed it into DLog and everything worked fine. But you seem to have it correct. Make sure your Prefix.pch file is included in 'Build Settings' -> 'Prefix Header' 来源： https://stackoverflow.com/questions/9799838/arc-warning-implicit-declaration-of-function-dlog-is-invalid-in-c99

id __weak obj1 = obj0; equals id __weak obj1 = obj0; id __autoreleasing tmp = obj0; In Pro multithreading and memory management for iOS and OSX . But why the obj1 need to add to the autorelease pool, I think making a weak pointer of an object should not affect its lifetime. { NSObject* sp = [NSObject new]; NSObject* __weak wp = sp; } the above code is translate to: id sp = objc_msgSend(NSObject, "new"); id wp; objc_initWeak(&wp, sp); objc_destroyWeak(&wp); objc_storeStrong(&sp, 0); 1) obj_initWeak merely associate the weak pointer wp with the strong pointer sp to ensure that when the object

With all this new ARC stuff (which does not fall under NDA…) coming out, it seems like the default for dealing with properties is to set the property without and ivar in the implementation file explicitly until you synthesize it with something like: @synthesize var = _var; What's the best practice to use in setting the variable? I know the difference between var and self.var is that self.var is using dot notation and is using the var's setter method. Is _var just the equivalent of setting it up within the header files like in the good ol' days? Where did that practice of prefacing everything

Is there some of documentation how the compiler auto-generates the accessors of properties? When writing custom accessors (overriding the synthesized ones), it would be nice to know the original implementation. Especially to see the differing implementations of accessors for properties with different (weak/strong/retain/copy etc..) attributes. Is there some of documentation how the compiler auto-generates the accessors of properties? The compiler just adds a C function call. Peek at the asm (e.g. _objc_getProperty and _objc_setProperty ). When writing custom accessors (overriding the