On Jul 7, 2011, at 4:03 PM, Jens Alfke wrote: > 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.
This is less safe than you might like. On iOS and 64-bit Mac, you may end up with both copies of the class in use simultaneously. That means two separate invocations of +initialize, two separate locks for @synchronized([MyClass class]), etc. The simplest solution is to keep your utility classes in a static archive on iOS, but build it as a dylib for Mac OS. -- Greg Parker gpar...@apple.com Runtime Wrangler _______________________________________________ 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
