automatic-ref-counting

When trying to use -retain , -release , and -dealloc while building my application using automatic reference counting in Xcode 4.2, I get an error like the following: Automatic Reference Counting forbids explicit message send of 'dealloc' Why am I seeing this error? Are -retain , -release , and -dealloc no longer allowed under automatic reference counting? Basically: When using ARC, it's all or nothing. Either the compiler is managing all of the retains/releases/deallocs for you, or it is doing nothing. You cannot intersperse your own calls to them, because the compiler wants to do it all

I recently started a new project using Automatic Reference Counting (ARC). When I assigned the contents of a CALayer: UIView* view = ... UIImage* image = ... view.layer.contents = image.CGImage I got an error Implicit conversion of a non-Objective-C pointer type 'CGImageRef' to 'id' is disallowed with ARC Simply casting the CGImageRef to id hides the error, but I was wondering if the ARC still functions correctly then? Steve You should really check out the ARC videos from WWDC 2011. They are available on the developer site and open through iTunes. Especially: • Session 323 – Introducing

I'd like to store an array of weak references in Swift. The array itself should not be a weak reference - its elements should be. I think Cocoa NSPointerArray offers a non-typesafe version of this. Create a generic wrapper as: class Weak<T: AnyObject> { weak var value : T? init (value: T) { self.value = value } } Add instances of this class to your array. class Stuff {} var weakly : [Weak<Stuff>] = [Weak(value: Stuff()), Weak(value: Stuff())] When defining Weak you can use either struct or class . Also, to help with reaping array contents, you could do something along the lines of: extension

I am trying to understand the correct way of getting an NSString from a CFStringRef in ARC? Same for going the opposite direction, CFStringRef to NSString in ARC? What is the correct way to do this without creating memory leaks? Typically NSString *yourFriendlyNSString = (__bridge NSString *)yourFriendlyCFString; and CFStringRef yourFriendlyCFString = (__bridge CFStringRef)yourFriendlyNSString; Now, if you want to know why the __bridge keyword is there, you can refer to the Apple documentation . There you will find: __bridge transfers a pointer between Objective-C and Core Foundation with no