Geek Answers Handbook

Too early to use ARC for new projects?

I am about to start a new project, and I am wondering whether to use ARC or not.

I don’t know if he recommended using ARC when I know that the new project will have quite a few dependencies on older code and external libraries that have not yet been converted to ARC (three20, shareKit, ASIHTTPRequest, ..)? Some of the libs are quite large, so I think it would be tedious to add the -fno-objc-arc flag for each individual file.

It seems that Apple has taken the ARC path specifically for iOS, and every iOS developer will have to convert sooner or later.

But maybe it's too early to jump onto the ARC bandwagon yet?

+5
source share
1 answer

Compiled libraries will work with ARC out of the box. All ARC automatically adds memory management. It will add save, releases, etc. If the code has already been compiled, it will contain the necessary memory management, regardless of whether it was compiled using ARC or not.

If you add third-party code directly to your application, you need to make sure that the code works with ARC, but you do not need to change anything for compiled libraries and frameworks.

Apple is pushing ARC as the way forward, so for a new project, I don't think there should be any problems with it.

+1
source

More articles:


All Articles