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

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

Ehm... What's wrong with setting $ENV{PATH} in a BEGIN block?

update

Providing you are not allowed to set the correct environment in the registry.

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)

Je suis Charlie!}

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

Replies are listed 'Best First'.
Re^4: Using STDIN after exec() with ActiveState Perl by Yaribz (Beadle) on Jun 21, 2015 at 20:00 UTC
The DLL to load is not known at script start.	[reply]
Re^5: Using STDIN after exec() with ActiveState Perl by LanX (Saint) on Jun 21, 2015 at 20:19 UTC
You are getting sarcastic answers because you are asking the wrong questions without providing enough informations even after multiple attempts. Please state your use case clearly, such that we can help you. See also How do I post a question effectively? PS: welcome in the.monastery! =) Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :) Je suis Charlie!}	[reply]
Re^6: Using STDIN after exec() with ActiveState Perl by Yaribz (Beadle) on Jun 21, 2015 at 20:39 UTC
you are asking the wrong questions without providing enough informations even after multiple attempts. Please state your use case clearly, such that can help you. I though I stated my problem quite clearly in the initial post? I'm just wondering if someone found a workaround concerning the side-effects of "exec" on STDIN when using ActiveState perl. Then people got curious about why I needed exec so I tried to answer them the best I could, what's wrong with that exactly?	[reply]
Re^7: Using STDIN after exec() with ActiveState Perl by LanX (Saint) on Jun 21, 2015 at 20:52 UTC
Re^5: Using STDIN after exec() with ActiveState Perl by Anonymous Monk on Jun 21, 2015 at 20:13 UTC
Great, then you don't need a begin block :)	[reply]

In Section Seekers of Perl Wisdom