> On 25 Feb 2016, at 17:43, Jens Alfke <j...@mooseyard.com> wrote: > > >> On Feb 25, 2016, at 8:35 AM, Dave <d...@looktowindward.com >> <mailto:d...@looktowindward.com>> wrote: >> >>>> Also, beware subclassing a Non-ARC Class in an ARC Project - you have to >>>> have the subclass Non-ARC too. >>> >>> This is not true. For example, NSView is not ARC but you can write ARC >>> subclasses of it. >> >> I didn’t say it was impossible, but depending on what the class does and how >> it’s implemented can cause problems…….. > > You did say “you have to have the subclass Non-ARC”, which to me sounds like > “it’s impossible”.
Sorry, I just re-read it and it was supposed to read *may* have to….. > And I can’t think of any way that a (properly implemented) non-ARC class > could cause problems for an ARC subclass. A class’s or method’s behavior > doesn’t change depending on whether its implementation uses ARC. Do you have > any actual examples of problems? > > —Jens Somewhere but it is back in the distant git-past and probably not that easy to find and I can’t remember why I had to do it now, something to do with properties and/or IVs. It may well have been possible to do it another way, but the easiest seemed to be to make it non-ARC too. _______________________________________________ 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
