AU, Obj-C and names
AU, Obj-C and names
- Subject: AU, Obj-C and names
- From: john smith <email@hidden>
- Date: Thu, 1 Oct 2009 12:48:26 +0200
- Importance: Normal
Hi,
so, looks like I cannot fight it off any longer... I have to move the rest of my code to Cocoa.
But... I just found this:
http://developer.apple.com/mac/library/documentation/Cocoa/Conceptual/LoadingCode/Tasks/NameConflicts.html
Now, I have a SDK which I use myself, and also other companies are using it. This SDK builds a static library, which is linked with the plug-in.
So, when I'm fully supporting Cocoa in this library, it seems that I'll have to deliver a new static library for each and every one of the plug-ins that are using it, just to avoid name clashes. It feels like I'm missing something here. Surely, this cannot be true?
(Note that I'm only using Obj-C inside the library, the library interface is C++, and will stay that way).
Thanks,
Michael Olsen
Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it!
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden