So the answer is "neither - rename closes the filehandle".
I think you missed the bit about "... two concurrent (Perl) processes ..." and "... when the second process next reads via it's open handle ..."
A better test would be
#!/usr/bin/perl
use strict;
use warnings;
open OUT, '>', 'junk.1' or die $!;
print OUT 'X'x 20 . "$_\n" for 1 .. 20;
close OUT;
open OUT, '>', 'junk.2' or die $!;
print OUT 'Y'x 20 . "$_\n" for 1 .. 20;
close OUT;
open IO, '+<', 'junk.1' or die $!;
seek IO, 0, 0;
print scalar <IO>;
system $^X, '-le', q[ print rename( 'junk.2', 'junk.1' ) ? 'worked' :
+'failed'];
print scalar <IO>;
seek IO, 0, 0;
print scalar <IO>;
close IO;
unlink 'junk.1';
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
-
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.
|