Yes, and that works with -i as well.
Doesn't seem to:
> perl -i.bak -pe "BEGIN{s!^(\s)!./$1!,s/^/</,s/$/\0/ for @ARGV} s/fo
+o/bar/" bar
Can't open <bar: No such file or directory.
> perl -v
This is perl, v5.10.0 built for cygwin-thread-multi-64int
(with 6 registered patches, see perl -V for more detail)
Putting '<' on the front breaks -i. Putting "\0" on the end breaks -i.bak. Prepending "./" (at least on platforms that support that directory syntax) doesn't break either use of -i, but that still leaves files that end with space or '|' out.
But I still boggle that you think it is better to make the 99% case this much harder while refusing to make the "cute hack" magical case any harder at all. So much for proper Huffman coding (much less defaulting to 'safe' behavior and requiring a slight acknowledgement for something dangerous).
echo > '"Reason for this Perl insanity?" || rm -rf .. |'
-
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.
|
