various documentation tweaks suggested by M. J. T. Guy

p4raw-id: //depot/perl@4616

diff --git a/INSTALL b/INSTALL
index 8014a41..1fc85c0 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -4,6 +4,10 @@ Install - Build and Installation guide for perl5.
 
 =head1 SYNOPSIS
 
+First, make sure you are installing an up-to-date version of Perl.   If
+you didn't get your Perl source from CPAN, check the latest version at
+<URL:http://www.perl.com/CPAN/src/>.
+
 The basic steps to build and install perl5 on a Unix system are:
 
        rm -f config.sh Policy.sh
@@ -28,8 +32,6 @@ on the platform.  If that's not okay with you, use
        make test
        make install
 
-Full configuration instructions can be found in the INSTALL file.
-
 For information on non-Unix systems, see the section on
 L<"Porting information"> below.
 

diff --git a/lib/strict.pm b/lib/strict.pm
index 940e8bf..99ed01d 100644 (file)
--- a/lib/strict.pm
+++ b/lib/strict.pm
@@ -56,6 +56,9 @@ L<perlfunc/local>.
 The local() generated a compile-time error because you just touched a global
 name without fully qualifying it.
 
+Because of their special use by sort(), the variables $a and $b are
+exempted from this check.
+
 =item C<strict subs>
 
 This disables the poetry optimization, generating a compile-time error if

diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 7cf4d3f..a68c7a0 100644 (file)
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -1199,8 +1199,8 @@ C<eof> without the parentheses to test I<each> file in a while
     }
 
 Practical hint: you almost never need to use C<eof> in Perl, because the
-input operators return false values when they run out of data, or if there
-was an error.
+input operators typically return C<undef> when they run out of data, or if
+there was an error.
 
 =item eval EXPR
 

diff --git a/pod/perlsyn.pod b/pod/perlsyn.pod
index 0dd842d..1f3ae50 100644 (file)
--- a/pod/perlsyn.pod
+++ b/pod/perlsyn.pod
@@ -163,6 +163,8 @@ If the LABEL is omitted, the loop control statement
 refers to the innermost enclosing loop.  This may include dynamically
 looking back your call-stack at run time to find the LABEL.  Such
 desperate behavior triggers a warning if you use the B<-w> flag.
+Unlike a C<foreach> statement, a C<while> statement never implicitly
+localises any variables.
 
 If there is a C<continue> BLOCK, it is always executed just before the
 conditional is about to be evaluated again, just like the third part of a