From: Robin Barker <RMBarker@cpan.org>
Date: Tue, 12 Mar 2002 13:31:58 +0000 (+0000)
Subject: Re[2]: Related issues? [ID 20020222.011]
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=efdd02185294f5c1e6e467a2fe3ee05432b42a84;p=p5sagit%2Fp5-mst-13.2.git

Re[2]: Related issues? [ID 20020222.011]
   Message-Id: <200203121331.NAA21278@tempest.npl.co.uk>

p4raw-id: //depot/perl@15198
---

diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 63d12d7..b32cd94 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -1276,7 +1276,10 @@ formed from the files listed on the command line and accessed via the
 C<< <> >> operator.  Since C<< <> >> isn't explicitly opened,
 as a normal filehandle is, an C<eof()> before C<< <> >> has been
 used will cause C<@ARGV> to be examined to determine if input is
-available.
+available.   Similarly, an C<eof()> after C<< <> >> has returned 
+end-of-file will assume you are processing another C<@ARGV> list,
+and if you haven't set C<@ARGV>, will read input from C<STDIN>;
+see L<perlop/"I/O Operators">.
 
 In a C<< while (<>) >> loop, C<eof> or C<eof(ARGV)> can be used to
 detect the end of each file, C<eof()> will only detect the end of the