Dave is working with a framework I wrote, which makes use of OmniGroup's "weak retain" concept from many years ago. See Ken Case's writeup at https://github.com/jnozzi/cocoadev.com/blob/888a4ffa2ab233762728d5e2f23c18a83feb3a6e/markdown/WeakReferences.md <https://github.com/jnozzi/cocoadev.com/blob/888a4ffa2ab233762728d5e2f23c18a83feb3a6e/markdown/WeakReferences.md>
There are more modern ways to do this now, but my framework has to work with older versions of macOS. In my framework, the "weak retain" stuff is used in the context of an accessibility API observer that watches for the destruction of an accessibility API user interface element. This is a context where circular retain counts must be dealt with. Bill > On Jan 25, 2017, at 10:55 AM, Mike Abdullah <mabdul...@karelia.com > <mailto:mabdul...@karelia.com>> wrote: > > You’re inevitably going to get asked this: > Why on earth are you overriding release? It’s an incredibly niche thing to > do, and the answer probably depends a lot on why you’re overriding it. -- Bill Cheeseman - wjcheese...@comcast.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
