Garbage Collection
Garbage Collection
- Subject: Garbage Collection
- From: Keith Duncan <email@hidden>
- Date: Wed, 23 Jan 2008 16:40:04 +0000
When compiling with garbage collection supported, is the garbage
collection status determined at runtime or compile time?
As far as I know it is decided when linking and the GC status is based
on whether the linked libraries support it or not. But take an
application which uses non-GC plugins for example, if all the linked
libraries DO support GC then the plugins which haven't been compiled
GC supported can't be loaded because they still depend on retain/
release logic.
So, a GC supported app can't be deployed in an environment where it
will load non-GC supported plugins. Is there anyway to defer the
enabling of GC until all dynamically loaded code has been loaded? From
my knowledge of theoretical GC, it can be turned on at any point in a
reference counted environment; but once on it cannot be switched off,
is this correct? And if so, is there a low-level API to perform such a
task?
Keith
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden