git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] change Perl syntax to support Perl 5.6

From
Avery Pennarun <apenwarr@gmail.com>
Date
Aug 31, 2008, 18:29 UTC
Message-ID
<32541b130808311129u79f4179enfabab8f5845ed522@mail.gmail.com>
In-Reply-To
<7v63ph40at.fsf@gitster.siamese.dyndns.org>
On Sun, Aug 31, 2008 at 12:27 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 25 quoted lines
> merlyn@stonehenge.com (Randal L. Schwartz) writes:
>
>>>>>>> "Avery" == Avery Pennarun <apenwarr@gmail.com> writes:
>>
>> Avery> Shell quoting is a disaster (including security holes, where relevant)
>> Avery> waiting to happen.  The above is the only sane way to do it, and it
>> Avery> isn't very hard to implement.  (Instead of system() in the subprocess,
>> Avery> you can use exec().)
>>
>> quotemeta() is about regex quoting.  This is not precisely the same as shell
>> quoting, and is both misleading, and potentially broken.
>
> Agreed to, and grateful for, both of your comments.
>
> Do you like the one Jakub quoted from how gitweb does it?  It looks like
> this:
>
>    # quote the given arguments for passing them to the shell
>    # quote_command("command", "arg 1", "arg with ' and ! characters")
>    # => "'command' 'arg 1' 'arg with '\'' and '\!' characters'"
>    # Try to avoid using this function wherever possible.
>    sub quote_command {
>           return join(' ',
>                       map( { my $a = $_; $a =~ s/(['!])/'\\$1'/g; "'$a'" } @_ ));
>    }

No, that's just another feeble attempt at quoting, which may or may not be correct. I'm not smart enough to tell.

I have a proper implementation in the 'runlock' script in gitbuilder:
    http://github.com/apenwarr/gitbuilder/tree/master/runlock

In that particular case, I wanted to handle signals carefully, so I needed the manual fork thing even in perl 5.8. You can safely remove the signal handling stuff (and of course the lockfile stuff) if you just want a minimal safe fork-exec-wait implementation in perl.

Have fun,
Avery
Previous: Junio C HamanoNext: Jakub Narebski
Message 12 of 29 in “change Perl syntax to support Perl 5.6”
  1. change Perl syntax to support Perl 5.6Robert Schiele, Aug 30, 2008
  2. Jeff KingAug 30, 2008
  3. Junio C HamanoAug 30, 2008
  4. Jeff KingAug 30, 2008
  5. Robert SchieleAug 30, 2008
  6. Jeff KingAug 30, 2008
  7. Jakub NarebskiAug 30, 2008
  8. Robert SchieleAug 30, 2008
  9. Avery PennarunAug 31, 2008
  10. Randal L. SchwartzAug 31, 2008
  11. Junio C HamanoAug 31, 2008
  12. Avery PennarunAug 31, 2008
  13. Jakub NarebskiAug 31, 2008
  14. Petr BaudisAug 31, 2008
  15. H. Peter AnvinSep 1, 2008
  16. Robert SchieleSep 1, 2008
  17. Tom G. ChristensenSep 1, 2008
  18. Brandon CaseySep 4, 2008
  19. Tom G. ChristensenSep 5, 2008
  20. Jakub NarebskiAug 31, 2008
  21. Jay SoffianSep 1, 2008
  22. Alex RiesenSep 1, 2008
  23. Avery PennarunSep 2, 2008
  24. Avery PennarunSep 2, 2008
  25. Junio C HamanoAug 30, 2008
  26. Randal L. SchwartzAug 31, 2008
  27. Ask Bjørn HansenAug 31, 2008
  28. Junio C HamanoSep 1, 2008
  29. Junio C HamanoSep 1, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.