;) I was being stupid in that example, I see how my ownership was still
retained until I called release (for NSTextView.alloc.initWithFrame) and
removeFromSuperview (for parent.addSubview). Since there's nothing strange with
NSTextView like I originally thought I just need to pay very close attention to
where I'm retaining it in my code.
Thanks guys.
On Jul 18, 2011, at 4:44 PM, Kyle Sluder wrote:
>> In trying to discover where I'm not balancing the reference counting I
>> noticed that calling removeFromSuperview in that example did NOT deallocate
>> the object after the autorelease pool was drained but after calling release
>> it did. The NSView docs state clearly the receiver is released but I claim
>> it was still retained. I'm tempted to say something is wrong with
>> NSTextView, but probably not. ;)
>
> Repeat after me: STOP THINKING ABOUT RETAIN COUNTS.
>
> If you follow the memory management rules, things will work.
Regards,
Ryan Joseph
thealchemistguild.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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
