> On Jul 12, 2017, at 2:57 PM, Jeremy Hughes <[email protected]> > wrote: > > I’m trying to understand memory management so I can avoid retain cycles and > other issues.
That’s fine. But using a weak reference to try to detect when an object gets dealloced is fraught with peril, viz. this entire thread :) If you want to find out if your code is leaking by creating reference cycles, just run it and ask either Instruments or Xcode to find leaks. —Jens _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
