Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

Re^2: Calling Windows Batch from Perl, double-quote appearing out of nowhere (insanity)

by rovf (Priest)
on Nov 09, 2012 at 15:26 UTC ( #1003160=note: print w/ replies, xml ) Need Help??


in reply to Re: Calling Windows Batch from Perl, double-quote appearing out of nowhere (insanity)
in thread Calling Windows Batch from Perl, double-quote appearing out of nowhere

Interesting point - this indeed explains (and it is also interesting that the quoting problem only shows up when we invoke the background version, but not the "normal" call to system).

It used to be that Perl's system() on Windows would trying running the command you gave directly first and would only resort to wrapping it in qq(cmd /c "...") if that failed. I think that, over the years, enough edge cases showed up that the details of this technique were changed in order to try to get more "expected behavior" in more cases.
Would this mean that in newer versions of Perl, the "foregroun" system() would show the same problem? I thought of using system() instead of system(1,...) and doing an explicit fork and exect, to avoid the quoting bug, but if newer Perl versions will consistently wrap the argument inside an extra invocation of cmd /c, the problem would reappear if I upgrade to a newer Perl :-(


-- 
Ronald Fischer <ynnor@mm.st>


Comment on Re^2: Calling Windows Batch from Perl, double-quote appearing out of nowhere (insanity)
Download Code
Re^3: Calling Windows Batch from Perl, double-quote appearing out of nowhere (insanity)
by tye (Cardinal) on Nov 09, 2012 at 15:36 UTC

    Just for y'all's information, I don't know the answer to that. It would be interesting to look into why only system(1,...) wraps things in cmd /c "..." in a way that triggers this bug. To figure that out, I'd read the code that I linked to above. I did scan some parts of it earlier but not looking for that quirk (I initially missed your point that the "1," was required).

    But why not just include a trailing space and then none of that will likely matter? (And include a comment noting that the trailing space is required to work around a bug in: cmd /c "cmd /c ...".)

    - tye        

      But why not just include a trailing space and then none of that will likely matter?

      Agreed! This indeed looks like the most sensible solution. (well, maybe the most sensible one would be to avoid Windows alltogether ;-)

      -- 
      Ronald Fischer <ynnor@mm.st>
        using one of the shellquoting modules I linked usually does the trick for me (keeps perl from fudging up the quoting)

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1003160]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (18)
As of 2014-09-16 14:00 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    How do you remember the number of days in each month?











    Results (24 votes), past polls