Re^19: Using STDIN after exec() with ActiveState Perl

Are there several processes running in parallel that use different version of the library?

If they are not parallel, instead of exiting after system returns, loop back up and determine the next set of ENV variable settings for the next run via system.

If several parallel sequential runs, just run as many "top level" instances of the top level Perl program as needed.

Comment on Re^19: Using STDIN after exec() with ActiveState Perl Select or Download Code

Replies are listed 'Best First'.
Re^20: Using STDIN after exec() with ActiveState Perl by Yaribz (Beadle) on Jun 23, 2015 at 20:04 UTC
Several instances are usually running in parallel and might be using different versions of the library, yes. The next set of ENV variables would be known by the child process but not the idle "top level" one, so I would have to pass back the info to the parent process. It would be a possible workaround indeed, but I prefer the "simplicity" of the workaround I'm using right now which simply avoids exec/system when running on Windows (cf Re^20: Using STDIN after exec() with ActiveState Perl). But thanks again nonetheless.	[reply]

Replies are listed 'Best First'.

Re^20: Using STDIN after exec() with ActiveState Perl
by Yaribz (Beadle) on Jun 23, 2015 at 20:04 UTC

Several instances are usually running in parallel and might be using different versions of the library, yes.

The next set of ENV variables would be known by the child process but not the idle "top level" one, so I would have to pass back the info to the parent process. It would be a possible workaround indeed, but I prefer the "simplicity" of the workaround I'm using right now which simply avoids exec/system when running on Windows (cf Re^20: Using STDIN after exec() with ActiveState Perl).

But thanks again nonetheless.

[reply]