I doubt this is possible in Cocoa as it is currently implemented.
For example, the Cocoa framework doesn't release several singletons
(the most prominent of which are the application delegate and the
other objects in the MainMenu.nib). So, pretty much every app will
have a good number of "leaks" on exit.
I guess this was my original point, though Uli has phrased it far
better than I did.
Of course those are irrelevant in the end, because the
application's memory will be torn down anyway, but it's a bunch of
work to detect what objects are intentional leaks (e.g. not just
the app delegate, but also all objects "hanging off of it").
This is assuming the OP did in fact mean (as I interpreted it) he
wants to check it on the termination of application. I believe that
to be the case. :-)
On Mar 14, 2007, at 7:40 PM, John Stiles wrote:
In my world, that is the traditional model...
I do realize you said "non-ObjC", so I can see how that'd work,
but the points mentioned above are salient for an ObjC Cocoa
application. Perhaps it's best if the OP steps in and clarifies
exactly what he's trying to do. :-)
--
I.S.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
