RE: Advice for Cocoa Plug-ins & Objective-C implementation uniquing
RE: Advice for Cocoa Plug-ins & Objective-C implementation uniquing
- Subject: RE: Advice for Cocoa Plug-ins & Objective-C implementation uniquing
- From: john smith <email@hidden>
- Date: Fri, 5 Feb 2010 07:57:35 +0100
- Importance: Normal
It's possible to dynamically generate a class at runtime. That way it's reasonably easy to give the class a semi-random name.
In my code I have objc code in 2 places. One of them is in a static library, just like you, and here I chose the path mentioned above. This is because there's not a lot of code (to me doing Cocoa means "Implement as little Obj-C as possible").
The other place is in the AU specific code (which lives in a separate binary). Here I havn't solved the problem yet, but I expect to use macros to rename the classes (since I need a build/target per product anyway).
I agree that using frameworks is the wrong solution; it is an incredible overkill in my opinion.
Anyway, what I'm trying to say is: If your classes are reasonably small, you may want to look into dynamically created classes. Sure, it's a drag, and it's much more code that we're used to, but hey, it's Obj-C ,-)
Cheers,
Michael Olsen
PhonoXone
|
_______________________________________________
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