in reply to Re^4: 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.

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

  • Comment on Re^5: Using STDIN after exec() with ActiveState Perl

Replies are listed 'Best First'.
Re^6: Using STDIN after exec() with ActiveState Perl
by Yaribz (Beadle) on Jun 21, 2015 at 19:59 UTC
    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.
[reply]
      here you go system $^X, $0 ;
[reply]
[d/l]
        If I use system then I will end up with tons of perl processes (one for each DLL change).
[reply]
[d/l]

      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

[reply]
        I use a Perl module built with Swig, which implements the interface with a dynamic library coded in C++. I need to use this module with different versions of the C++ library, so what I do is: set the PATH environment variable according to the desired library version, use exec so that this environment variable is taken into account (it doesn't work otherwise), then require the module generated by Swig
[reply]

In Section Seekers of Perl Wisdom