Re: why does this leak?
Re: why does this leak?
- Subject: Re: why does this leak?
- From: Erik Buck <email@hidden>
- Date: Mon, 13 Feb 2006 20:35:49 -0500
if somebody tells me THIS is not a cocoa question, i'll simply stop
getting this list.
I can't resist an ultimatum! This is not a Cocoa question.
How do you know there is a leak ?
Mac OS X menu's are (as far as I can tell) implemented as truly
frightful bastardized not-quite Carbon legacy compatibility kludges
that have never worked completely right from Cocoa and lost a lot of
Openstep functionality that used to work even on Windows NT.
OK, I concede that Cocoa's reference counting conventions are
probably involved in the question. It is worth noting the Core
Foundation also uses reference counting. (So does MFC CString, COM/
DOM, etc. just for reference) If you are not following the simple
Cocoa conventions, all bets are off and leaks or crashes will surely
result. It is not your problem how menu's work and how many times
they might be retained. If you balance your implicit and explicit
retains with releases or autoreleases, you won't have a problem.
"Very simple rules for memory management in Cocoa"
http://www.stepwise.com/Articles/Technical/2001-03-11.01.html
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden