Some questions about Automatic Reference Counting in iOS5 SDK

I'm currently developing an app for iPad. The development started for iOS 4.2 and is now continuing (and I think will be completed) for iOS 4.3. I just read about ARC in iOS 5, and basically I understood that we will never need to release and retain objects anymore. My questions are:

1. If I decide to upgrade to iOS 5, do I need to remove all [myObject retain] and [myObject release] statements from my code?

2. If I develop a new app for iOS 5 using ARC, will I need to implement some sort of "retro-compatibility" checks? i.e.: will I need to check the version of iOS and call retain and release accordingly? So, basically, is ARC available for all iOS versions or just for iOS 5?

> If I decide to upgrade to iOS 5, do I > need to remove all [myObject retain] > and [myObject release] statements from > my code?

Yes, but XCode 4.2 includes a new "Migrate to Objective-C ARC" tool (in the Edit->Refactor menu), which does that for you. Calling dealloc is a different story. As mentioned in the comments the clang reference states that you should keep your the dealloc method:

Rationale: even though ARC destroys instance variables automatically, there are still legitimate reasons to write a dealloc method, such as freeing non-retainable resources. Failing to call [super dealloc] in such a method is nearly always a bug.

> You enable ARC using a new -fobjc-arc > compiler flag. ARC is supported in > Xcode 4.2 for Mac OS X v10.6 and v10.7 > (64-bit applications) and for iOS 4 > and iOS 5. (Weak references are not > supported in Mac OS X v10.6 and iOS > 4). There is no ARC support in Xcode > 4.1.

> If I develop a new app for iOS 5 using > ARC, will I need to implement some > sort of "retro-compatibility" checks? > I.e.: will I need to check the version > of iOS and call retain and release > accordingly? So, basically, is ARC > available for all iOS versions or just > for iOS 5?

No, because ARC does its magic on compile time and not on run time.

> > Instead of you having to remember when > to use retain, release, and > autorelease, ARC evaluates the > lifetime requirements of your objects > and automatically inserts the > appropriate method calls for you at > compile time. The compiler also > generates appropriate dealloc methods > for you.

Further Information on ARC: http://clang.llvm.org/docs/AutomaticReferenceCounting.html

Q1: NO, If you have an existing code, you can keep using it as is with the -fno-objc-arc you can selectively disable ARC on any file.

If you want to disable ARC on MULTIPLE files:

1. Select desired files at Target/Build Phases/Compile Sources in Xcode
2. PRESS ENTER. (double click selects only one file)
3. Type -fno-objc-arc
4. Press Enter or Done

Q2: NO, target can be as low as iOS 4.0

As far as I understand and as far as my iPhone/iPod running iOS 5 and iOS 4.3 respectively work, it's all quite automatic. An app I started for 4.0 and have "updated" to work with Xcode for iOS 5.0 never throws any sort of warning my way about releasing and retaining, even though it's all over every dealloc, etc. However, some of the same code I inserted (copied the file) into a new project created with Xcode for iOS 5 has many, many warnings. So it appears you don't have to remove all those calls, and no, it somehow adapts it automatically for older versions. Profiling my iPod, I see no memory leaks or other signs of failing deallocs/releasing. Does this help?

Regarding this part of your question

> If I develop a new app for iOS 5 using ARC, will I need to implement > some sort of "retro-compatibility" checks? I.e.: will I need to check > the version of iOS and call retain and release accordingly? So, > basically, is ARC available for all iOS versions or just for iOS 5?

It should be be noted that the iOS 5 compiler takes of the "retro-compatibility" (it actually ADDS the code to make retain/release work, essentially), but if you are not compiling for iOS 5.0, you cannot use weak as a keyword. Instead you use assign. This is unfortunate: weak is a huge advantage (no dangling pointers, ever!). See my question here for a discussion of weak, assign and ARC.

If you can disable ARC by not using the new -fobjc-arc compiler flag, then you are not forced to re-write code moving forward - I guess (?)