in reply to Re^3: Using STDIN after exec() with ActiveState Perl
in thread Using STDIN after exec() with ActiveState Perl

I know. I use PATH instead on Windows and it works. The only problem is this STDIN being multiplexed.

edit: actually it's not even for the PATH environment variable that I need the exec, it's for setting an environment variable that can be seen by a dynamic library called by my script.
  • Comment on Re^4: Using STDIN after exec() with ActiveState Perl

Replies are listed 'Best First'.
Re^5: Using STDIN after exec() with ActiveState Perl
by Anonymous Monk on Jun 21, 2015 at 19:49 UTC

    I know. I use PATH instead on Windows and it works. The only problem is this STDIN being multiplexed.

    Windows isn't linux, PATH is not LD_LIBRARY_PATH , you don't need exec on windows

      I know Windows isn't linux, and I know PATH is not LD_LIBRARY_PATH. However I didn't know it was possible to set an environment variable that can be seen by a dynamic library loaded by a perl script without relying on using exec, which is what you meant by "you don't need exec on windows" I guess. If you have any link containing information about how to do that I would be very interested.
        here you go system $^X, $0 ;

        dynamically select a specific DLL to load from a perl script without

        What do you mean by that?

        Any "dynamically load a dll" code ought to take an absolute path to said dll