Strategies to prevent class name clashes
Strategies to prevent class name clashes
- Subject: Strategies to prevent class name clashes
- From: Arne Scheffler <email@hidden>
- Date: Fri, 15 Feb 2008 10:09:55 +0100
Hi,
I'm just porting an open source UI toolkit to Cocoa. This toolkit is
mainly used in plug-ins by many different people. So it's more than
likely that two or more plug-ins get loaded into the same process.
It's also very common that the people who uses the toolkit modify the
source. This all worked in C++ because all bundles were loaded into
different name spaces. With Objective-C this is no longer the case. I
already got a problem while porting that two plug-ins that uses the
toolkit were compiled at different times with different code. But as a
nature of Objective-C it only loaded the classes once. I'm looking now
for a way to prevent this. Does anyone have any idea how to best deal
with this ?
thanks
arne
_______________________________________________
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