Sorry, you have confused me slightly (or perhaps given me false hope). I have 3 targets in my project: (1) the preference pane; (2) a framework; and (3) an application.
1 & 2 are both dual mode insofar as they can be compiled and run without garbage collection. #3, which doesn't interact with the System Prefs, but uses code out of the framework (#2), requires GC. I thought the point of "supported" versus "required" compile options for frameworks was that the first would support a GC app, but not require it, and the second would...well...require it. So, if a non-GC pref pane is loading a "GC-Supported" framework, shouldn't it be GC-free? Is the only way to do this to have entirely separate versions of the framework? (or just put the same code in each target separately and dispense with a a framework)? > From: Bill Bumgarner <b...@mac.com> > Date: Fri, 27 Feb 2009 11:08:27 -0800 > To: Nick Zitzmann <n...@chronosnet.com> > Cc: Tobias Zimmerman <automa...@gmail.com>, "cocoa-dev@lists.apple.com" > <cocoa-dev@lists.apple.com> > Subject: Re: NSPrefrencePane with Garbage Collection won't work in System > Preferences? > > On Feb 27, 2009, at 11:00 AM, Nick Zitzmann wrote: >> The PreferencePanes framework in Leopard doesn't support GC for some >> unknown reason. I believe I filed a bug on this when it was in early >> beta, and nothing changed in the final. > > The System Preferences application does not support GC, thus framework > support is irrelevant. > > An application is either GC'd or non-GC'd; all or none for all > frameworks and bundles loaded. > > Applications *can* be compiled dual-mode, but it is generally > discouraged as there is no real point to doing so and would require re- > launching to switch modes. > > b.bum > > > _______________________________________________ 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
