Re: Is it my ENV within my system call or the shell itself?

Just backtick something like perl -le'print for %ENV' and see what the %ENV looks like. I also seem to recall that Perl doesn't necessarily go through the shell anymore even for backticks - if that's the case, you'll need another way of invoking Perl on the file as Windows itself cannot be made to honour the shebang line. The easiest solution, it seems, would be to just qx/perl scriptname/.

Makeshifts last the longest.

Comment on Re: Is it my ENV within my system call or the shell itself?

Replies are listed 'Best First'.
Re: Re: Is it my ENV within my system call or the shell itself? by BrowserUk (Patriarch) on Oct 02, 2003 at 22:21 UTC
...Windows itself cannot be made to honour the shebang line. CMD doesn't honour the shebang line, but the MKS shell for Win32 does. The only problem was persuading perl to use the right shell. The PERL5SHELL envvar takes care of that nicely. Examine what is said, not who speaks. "Efficiency is intelligent laziness." -David Dunham "When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller If I understand your problem, I can solve it! Of course, the same can be said for you.	[reply]
Re^3: Is it my ENV within my system call or the shell itself? by Aristotle (Chancellor) on Oct 02, 2003 at 23:49 UTC
Not only `CMD.EXE`, but Windows as a whole. Launching executables using a system call is bound to the filename extension. Nevertheless, if Perl is indeed going through the shell in this case, then of course that offers a potential solution which did work in your case. Makeshifts last the longest.	[reply]