Change 15198 by ams@lustre on 2002/03/12 15:00:44
Subject: [PATCH perlfunc.pod] Re[2]: Related issues? [ID 20020222.011]
From: Robin Barker <[EMAIL PROTECTED]>
Date: Tue, 12 Mar 2002 13:31:58 GMT
Message-Id: <[EMAIL PROTECTED]>
Affected files ...
.... //depot/perl/pod/perlfunc.pod#302 edit
Differences ...
==== //depot/perl/pod/perlfunc.pod#302 (text) ====
Index: perl/pod/perlfunc.pod
--- perl/pod/perlfunc.pod.~1~ Tue Mar 12 08:15:05 2002
+++ perl/pod/perlfunc.pod Tue Mar 12 08:15:05 2002
@@ -1276,7 +1276,10 @@
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
End of Patch.
