On Mon, Apr 26, 2010 at 2:14 PM, vincent habchi <vi...@macports.org> wrote: > I am unable to see a NSManagedObject go through the dealloc: method, even > after its removal from the MOC. It seems these objects are created after a > initWithEntity:insertIntoMOC: with an initial retain count of 2, and, of > course, it is impossible to make the retain count (by honest means) drop > below 2. Is this normal expected behavior?
As far as you're concerned, it's perfectly valid behavior for every object in your application to never see -dealloc called, ever. As long as you are playing by the memory management rules, you shouldn't care one whit about when -dealloc is called. Those who work with -finalize in a GC environment are already familiar with this drill. If your object is holding on to some resource which you need it to release, write a method called -invalidate or -letGoOfImportantThing or something and call that at a deterministic time. --Kyle Sluder _______________________________________________ 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
