From: Rick M. <obj...@gm...> - 2008-09-18 12:46:52
|
On Thu, Sep 18, 2008 at 3:43 PM, Mark Miesfeld <mie...@gm...> wrote: > On Thu, Sep 18, 2008 at 12:28 PM, Rick McGuire <obj...@gm...> wrote: > >> It would require a little manual processing in the resolution code, >> but we could have the code search the REXX_PATH for the library as >> well. It would be nice if we did this for Windows too, but I'm not >> sure what's involved there. > > It would be nice to be able to load library packages that were in the REXX_PATH. > > Both dlopen and LoadLibrary will open the library given its full path > name. So, if we searched the REXX_PATH for the file and found it, the > full path name could be used and it should work the same on Windows. > > Windows also has a function, SetDllDirectory() which you can use to > add paths to the default DLL search path. Once you augment the path, > it stays that way for the life of the process. On Windows, we could > augment the DLL search path with the REXX_PATH directories on startup > and REXX_PATH would automatically be used for the library search. I saw that, but I'm not sure that's the behavior we want. To start with, it's not dynamic (i.e., you can't change it from inside a running ooRexx program). It's also not stable. Some other library we load might augment (or even worse, reset) the search path, which would mess things up. Rick > > -- > Mark Miesfeld > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |