If that wasn’t called out clearly in that non-ARC class’s documentation/header, then that non-ARC class was Doing It Wrong(tm).
> On May 13, 2016, at 2:55 AM, Dave <d...@looktowindward.com> wrote: > > Hi, > > The other thing to watch out for is if you have non ARC Classes in your > project, you can forget that they are using assign rather than weak for > properties (so the reference doesn’t get zeroed) that can lead to sending > message to objects that have been destroyed if you are not careful. You have > the same problem with Non-ARC of course, but once you have used ARC for a > while you tend to forger about the non ARC classes and expect it to work like > the rest of your App. I only say this, because I had a nasty bug that took > quite a while to find because I was assuming everything was ARC. > > Also I’ve found when converting from Non-ARC to ARC that in doing so can > reveal code smells and often you can simplify things….. > > All the Best > Dave > > > _______________________________________________ > > 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/bdurbrow%40rattlesnakehillsoftworks.com > > This email sent to bdurb...@rattlesnakehillsoftworks.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
