Re: NSLINKMODULE_OPTION_PRIVATE a problem? (OS X require of a modulemultiple times)

[Sam Roberts <sroberts@...>]

On Tue, Apr 03, 2007 at 01:08:26PM +0300, Asko Kauppi wrote:
> I may need to use named shared memory, or something, to actually get  
> the module instances know each other.  Given that the PRIVATE  
> behaviour is there to stay. It may still be best to have it like  
> this, requiring people who want the instances to know each other to  
> take the extra steps. We may need a wiki page on this?

You could write another .so, a tiny one containing only the shared
variable, and dlopen(_GLOBAL) it in your module. Might be easier to use
than named shared memory, particularly if you want sharing withing a
process, not sharing between processes.

Sam