On Jul 7, 2011, at 3:58 PM, Kenny Leung wrote: > Class XXXXX is implemented in both <your framework> and <Your app>. One of > the two will be used. Which one is undefined. > The same happens with dynamically loaded bundles, etc... > Is there any good way around this?
Not putting the classes into a static library. If you do, you end up with multiple copies of the classes, producing the warnings you’ve seen. If all copies of the classes are guaranteed to be built from the same code with the same build settings you’re probably OK, apart from the code bloat, but it still seems dangerous. > but then I worry about global variables... are there 2 versions of those? Yup, and depending on what they’re used for, that can quite likely cause nasty and hard-to-debug problems. —Jens_______________________________________________ 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
