On Tue, Mar 10, 2009 at 1:32 PM, Sean McBride <s...@rogue-research.com> wrote:
> You'll have to do a code review and testing of the framework's code to > make sure it supports both GC and RR. Unfortunately this is true. Not just for frameworks, but any plug-ins those frameworks might load. A new, small internal project started awhile back seemed like the perfect opportunity to try out GC in a production app. This app used QTKit, but users needed the Flip4Mac plug-in to work with WMA files. At the time (I have no idea about now), any time QuickTime tried to load the Flip4Mac plug-in, it would die horribly. I reverted to good old-fashioned memory management for two reasons: 1 - I couldn't wait for the plug-in to be updated to support this (assuming it ever would be). 2 - I could see no way of nicely handling the situation even if the plug-in was updated, since some users would inevitably be using an older version ... because they may have forgotten (or not even known) the plug-in was installed, or what it even was by name. I have to admit, it was a *totally* unexpected problem that I was lucky to have noticed (because I had the plug-in installed for personal use) before investing much time and having to retro-fit everything with memory management. If you're looking for more details (the specific failure, behavior, whether it could have been caught and handled properly), I have none. It was right around Leopard's release and was a quick-and-dirty project, so I didn't bother studying the problem beyond, "Oh, that won't work. Back to the tried-and-true". Sorry. -- I.S. _______________________________________________ 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
