Thanks Chris.
http://www.cocoabuilder.com/archive/message/cocoa/2008/2/17/199174
Has some info too. I see now where the problem lies. It sounds like a
framework is the proper approach, or is doing some OBJ-C runtime
hackery required to "uniquify" class names/descriptions during runtime?
Thanks,
On Apr 13, 2009, at 7:54 AM, Christopher Wright wrote:
oops, remembered one more option:
To properly handle this, you've got a few options:
* don't re-use classnames -- not what you want
* make sure shared functionality uses just C-functions, and mark
them as non-exported (the build option "Symbols Hidden By Default"
under "Code Generation" will do this for you) -- you can also mark
as non-exported via __attributes__ ((visibility("hidden"))) or
something, but that seems much more annoying, and doesn't always do
what I've wanted.
* for obj-c reuse, use a framework instead of in-code stuff.
* mark C-functions as static -- this works only if all references
to that function live in the same source file ("compile-unit local
scope" I think the term is), but it will also keep linking stuff
from stepping on symbols defined elsewhere.
--
[ christopher wright ]
[email protected]
http://kineme.net/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [email protected]
