Re: ARGV and read

Message-Id: <200109201221.NAA04258@gizmo.fdgroup.co.uk>

p4raw-id: //depot/perl@12094

diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index b4d2a82..aa8545b 100644 (file)
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -330,6 +330,8 @@ has changed. Detecting a change is perhaps the difficult bit.
 
 =head2 All ARGV input should act like E<lt>E<gt>
 
+eg C<read(ARGV, ...)> doesn't currently read across multiple files.
+
 =head2 Support for rerunning debugger
 
 There should be a way of restarting the debugger on demand.

diff --git a/pod/perlvar.pod b/pod/perlvar.pod
index 524b91f..99d2960 100644 (file)
--- a/pod/perlvar.pod
+++ b/pod/perlvar.pod
@@ -1095,6 +1095,17 @@ lexical scope.  See L<bytes>.
 The name that the Perl binary itself was executed as, from C's C<argv[0]>.
 This may not be a full pathname, nor even necessarily in your path.
 
+=item ARGV
+
+The special filehandle that iterates over command-line filenames in
+C<@ARGV>. Usually written as the null filehandle in the angle operator
+C<< <> >>. Note that currently C<ARGV> only has its magical effect
+within the C<< <> >> operator; elsewhere it is just a plain filehandle
+corresponding to the last file opened by C<< <> >>. In particular,
+passing C<\*ARGV> as a parameter to a function that expects a filehandle
+may not cause your function to automatically read the contents of all the
+files in C<@ARGV>.
+
 =item $ARGV
 
 contains the name of the current file when reading from <>.