Eventually, everyone working in a *nix environment will have to pass things to the shell, but as everyone should be aware of by now, most homegrown quoting solutions are inadequate and breakable. I spent some effort researching semantics to write one that isn’t. The only situation this snippet can’t cope with is null bytes, because the shell eats those without providing any way to preserve them.
It’s likely to be less efficient than substitution based approaches, but I also find it a lot clearer and cleaner. Regex-based solutions feel to me like careful fiddling. This one is easy to grok, and any edge cases would be easily apparent (there aren’t any); when it comes to a job as critical as this one I’ll take the obviously deficiency-free approach over the fast one any day.
sub shell_quote {
return join ' ', map {
( defined && length )
? join q[\\'], map { (length) ? qq['$_'] : q[] } split /'/
+, $_, -1
: q[''];
} @_;
}
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|