Thirded. I thought I wouldn't like it. As soon as I didn't have to manage retains and releases of temporary objects, the discipline completely left my mind. Now whenever I go back to non-ARC code I invariably make a ton of memory management errors, most of which are caught by the analyzer.
--Kyle Sluder On Sep 8, 2013, at 11:18 PM, Alex Kac <a...@webis.net> wrote: > Bingo. We’ve been working with Cocoa/Obj-C for many years, and still we’d > find weird errors that would be caused by some over-released object. We cut a > ton of code with ARC, and in the end we saw reliability go up and actually > even some performance. > > ARC is a win. The only place it really got a bit hairy was CF objects. I wish > ARC would work with them a bit more. > > On September 8, 2013 at 11:56:10 PM, Jens Alfke (j...@mooseyard.com) wrote: > > They’re a _lot_ easier. It might not look that way when you’re reading about > all the details, or converting existing code, because then you’re focusing on > the rare edge cases. But for the most part when actually coding you can > simply ignore ref-counting. Your code becomes more compact and readable, and > you’re less likely to make mistakes. > Alex Kac - President and Founder > Web Information Solutions, Inc. > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/kyle%40ksluder.com > > This email sent to k...@ksluder.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
