It’s best to use ARC uniformly in a project and not mix with non-ARC modules. Xcode has a tool to upgrade projects to ARC. I have used it a number of times, and it seems to do a very good job.
David > On Jan 30, 2015, at 8:15 PM, Jerry Krinock <je...@ieee.org> wrote: > > >> On 2015 Jan 30, at 10:08, Trygve Inda <cocoa...@xericdesign.com> wrote: >> >> Do you see non-ARC code becoming obsolete? > > Non-ARC code is already obsolete, but what I think you mean is will non-ARC > code fail to compile or run in some future OS version. Never say “never” > with Apple, but in this case, I don’t think so, because ARC is a layer on top > of non-ARC. > >> I could probably start moving it >> to ARC slowly but it is hard to justify time spent on something that is not >> really needed. I have not run into any serious bugs or unexplained crashes >> due to messed up retain/release. > > Then don’t touch it. Use ARC for new code. > > > > > _______________________________________________ > > 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/rowlandd%40sbcglobal.net > > This email sent to rowla...@sbcglobal.net _______________________________________________ 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
