Mar 6, 2002, 1:30 AM
Post #1 of 2
I'm using Perl v5.6.1 under WinNt 4.0 in a Dos box.
Avoiding shell escapes
Inside the Perl script, I need to call a batch file (<name>.bat), which sets all kinds of things - what it actually does is beyond my scope. I need those settings to continue with my own Perl script.
My problem: this batch file is invoked in a different shell, i.e. all the environment settings are copied, and using this copy, the batch file is executed. It is also on that copy that changes are made. When the program ends, the copy is destroyed, leaving Perl with an unmodified environment, which is, in this case, highly indesirable.
Is there any way to circumvent this, I mean, to let the batch file make the changes on the same environment as my Perl script uses?