in reply to Re^3: Executing perl program from another perl program and capturing the output
in thread Executing perl program from another perl program and capturing the output

And that's *all* that is required. No ifs; no buts; learn the rules, and it just works.

Yeah, I stick to learning perl quoting rules, and then don't worry about cmd.exe quoting rules too much

  • Comment on Re^4: Executing perl program from another perl program and capturing the output

Replies are listed 'Best First'.
Re^5: Executing perl program from another perl program and capturing the output
by BrowserUk (Patriarch) on Nov 25, 2014 at 05:00 UTC
    I stick to learning perl quoting rules,

    That's all I'm asking you to do.

    If the backticks command needs double quotes, then you need to precede them with a backslash. That's standard "perl quoting rules".

    Of course, knowing that the command needs double quotes on Windows (rather than single quotes on *nix), requires an open mind and a desire to understand.

    Trying to apply standard English grammar or pronunciation rules to French (or Dutch or German or Russian) ... is pointless.

    Equally, trying to "speak *nix" to Windows, is like the archetypal Englishman, speaking English, S-L-O-W-L-Y A-N-D L-O-U-D-L-Y, to "dear 'ol johnny foreigner", regardless of his nationality.

    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".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom