in reply to Re^5: Windows environment variable not set if calling from a perl program (goto :end)
in thread Windows environment variable not set if calling from a perl program

Thank you for the clarification. I learnt a new thing today. So it is impossible to manipulate Perl NOT to start a copy of cmd.exe right? I mean perl always starts a copy of cmd.exe which I don't know is preferred or not. But I know now it is not possible to do this. :)
  • Comment on Re^6: Windows environment variable not set if calling from a perl program (goto :end)

Replies are listed 'Best First'.
Re^7: Windows environment variable not set if calling from a perl program (goto :end)
by BrowserUk (Patriarch) on Dec 08, 2015 at 19:20 UTC

    Perl cannot run batch commands; only cmd.exe can run them -- ie. cmd.exe is the interpreter for batch commands, just as perl is the interpreter for Perl code -- so no; if you want run a batch file, it has to be done by cmd.exe.


    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
    In the absence of evidence, opinion is indistinguishable from prejudice.