apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan <...@wikifamilies.info>
Subject Re: [PATCH] apr_dso_open()
Date Mon, 09 Jan 2006 16:35:07 GMT
Joe Orton wrote:

>On Fri, Jan 06, 2006 at 12:05:36PM -0800, Jonathan wrote:
>  
>
>>LOCAL|NOW and GLOBAL|NOW only changes symbol depth. GLOBAL|NOW and 
>>LOCAL|LAZY allows symbol breadth and namespace breadth. I suggest 
>>another function, apr_dso_open_ex(), if we want more OS specific 
>>options. LOCAL|LAZY, however, is portable in likeness across other 
>>supported systems without dlopen().
>>    
>>
>
>Is that true for *all* the supported platforms, Win32, OS/2, Netware, 
>OS/390, etc etc?
>
>joe
>
>
>  
>
Here are some comments:

    * Win32 -defaults to private/local, has compile-time definitions for
      export/import (if supplied) otherwise run-time import is standard
      [I've tested]
    * OS/2 - defaults to private/local, compiler option to install
      automatic handler
    * OS/390 - defaults to private/local, various compile-time
      environments (some may default to  automatically add routines to
      add run-time export/import automation)
    * BeOS - defaults to private/local, assumed compile-time options
      available
    * Netware - has dlopen()
    * AIX (older)- simulated by lower-level routine/accesss, able to
      modify to make symbols not global
    * Darwin 10.1 - has NSAddImage() for private/local [I've tested]
    * Darwin 10.2 - has NSLINKMODULE_OPTION_PRIVATE on NSLinkModule()
    * Darwin 10.3 - has dlopen()
    * HP - has BIND_DEFFERED and shl_findsym()
    * linux/unix with dlopen() - yes [I've tested]

Please, let me know if I have missed any.
Jonathan


Mime
View raw message