Re: Why do we use -fobjc-arc instead of removing code with #define?
Re: Why do we use -fobjc-arc instead of removing code with #define?
- Subject: Re: Why do we use -fobjc-arc instead of removing code with #define?
- From: Uli Kusterer <email@hidden>
- Date: Mon, 25 Jun 2012 09:53:57 +0200
On 24.06.2012, at 05:55, Jerry Krinock wrote:
> Why didn't Apple do the same thing for ARC?
Because the whole point of ARC is that you don't have to write retain/release calls, and thus can't make mistakes in them. Since, once compiled, ARC code is pretty much identical to manually managed code (and you can mix and match ARC and manually managed modules), there really is no point in using ARC if you're then going to add manual calls anyway. That would only cause your code to exist in two versions (ARC and non-ARC) with two different sets of possible memory management bugs. So not only are you STILL writing manual-managed code, you've now also DOUBLED your QA load.
Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
http://www.masters-of-the-void.com
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden