Strategy for using common classes in multiple Cocoa plug-ins?
Strategy for using common classes in multiple Cocoa plug-ins?
- Subject: Strategy for using common classes in multiple Cocoa plug-ins?
- From: "Mark Munz (DevList)" <email@hidden>
- Date: Sat, 21 May 2005 12:18:36 -0500
I think my previous questions were a bit confusing, so I thought I'd
take another shot at it.
In an earlier discussion, it was pointed out that Cocoa classes all
share the same namespace per process. The problem I'm realizing is
that I have some common utility classes that I'm using that are used
in several plug-ins (and will be sharing the same space).
I'm wondering what the best strategy for dealing with this issue is
in writing these plug-ins?
Is the only option to revert to C functions? The document said that
globals share the same name space, but is that all globals (as in
static variables)? Or is it only exported globals that can cause
conflicts?
Most of the Cocoa code I've written are applications, so I haven't
had to deal with this, but I tried to find some discussions on the
topic and couldn't. Perhaps I'm not looking in the right place.
Thanks.
Mark Munz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden