All this leads me to the paragraph about top-level objects under
garbage collection:
===
Mac OS X - garbage collected memory model
Most objects in the graph are kept in memory through strong references
between the objects. Only the top-level objects in the nib file do not
have strong references initially. Thus, your code must create strong
references to these objects to prevent the object graph from being
released.
===
Does this mean that there's a race between the NIB loader's need to
create a strong reference and the GC thread's imperative to collect
the object before it is referenced?
— F
_______________________________________________
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
