comment on

Thanks, you're right.

Just for the record: I had confused myself unnecessarily by not putting a separator in between the cat of file1 and file2. Which made me wonder why the magical file handle is only being advanced by eof() at the very end, and not at every file boundary. When you do it properly, however, i.e. something like

cat file1
echo ---
cat file2
[download]

the output is

...
--- perl output to stdout ---
line3
opt=bar
--- cat after ---
line1
line2
---
line3
line1
line2
[download]

which shows that line3 of the first file does in fact belong to file2 after the processing...

P.S. I've now settled on suggesting my collegue

perl -i -pe '$f||=s/opt=.*/opt=bar/; $_.="opt=bar\n" if !$f && !@ARGV 
+&& eof' files...
[download]

(but unfortunately it took a little too long to get working to leave an "it's easy with Perl" impression — that's my fault, however :)

In reply to Re^4: perl -i -pe ... with eof() testing by Anonyrnous Monk
in thread perl -i -pe ... with eof() testing by Anonyrnous Monk

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.


Problems? Is your data what you think it is?
	PerlMonks