On Mon, January 4, 2010 12:39:22 PM Bill Bumgarner <b...@mac.com> wrote:
> It isn't so much thinking of it as a reference that needs to be nil'd out as
> much as it
> is a need to properly disconnect a subgraph of objects from the live object
> graph in
> an application such that the subgraph is collected. That is, "nil'ing out
> references" is
> a fix for a symptom where the overarching problem is one of properly managing
> the
> connectivity of the object graph within the application.
Does anybody know how the collector actually works? I've read the docs a dozen
times but something about the description makes me think it doesn't exactly
happen the way it's described. According to the docs, the collector "scans" all
of your objects to determine what needs to be deallocated. But in performing
this scan, how does it "know" which bits in your object are pointers to other
objects and which bits are just data?
I think that an understanding of what actually happens behind the scenes would
clear up a LOT of the common questions we see here about GC.
Soong
_______________________________________________
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
