[svn:perlfaq] r6628 - perlfaq/trunk

Author: comdog
Date: Sun Jul  9 05:46:14 2006
New Revision: 6628

Modified:
   perlfaq/trunk/perlfaq2.pod
   perlfaq/trunk/perlfaq3.pod
   perlfaq/trunk/perlfaq4.pod
   perlfaq/trunk/perlfaq7.pod
   perlfaq/trunk/perlfaq8.pod

Log:
* found instances of "below" that referred to other parts of the
perlfaq and changed to "later". Pagination and excerpts remove the
notion of spatial relationship, so we'll use a temporal one (even
though people may read this out of order :)


Modified: perlfaq/trunk/perlfaq2.pod
==============================================================================
--- perlfaq/trunk/perlfaq2.pod	(original)
+++ perlfaq/trunk/perlfaq2.pod	Sun Jul  9 05:46:14 2006
@@ -152,8 +152,8 @@
 If all else fails, consult http://perldoc.perl.org/ which has the
 complete documentation in HTML and PDF format.
 
-Many good books have been written about Perl--see the section below
-for more details.
+Many good books have been written about Perl--see the section later in
+L<perlfaq2> for more details.
 
 Tutorial documents are included in current or upcoming Perl releases
 include L<perltoot> for objects or L<perlboot> for a beginner's

Modified: perlfaq/trunk/perlfaq3.pod
==============================================================================
--- perlfaq/trunk/perlfaq3.pod	(original)
+++ perlfaq/trunk/perlfaq3.pod	Sun Jul  9 05:46:14 2006
@@ -762,11 +762,12 @@
 5.8 the Filter::Simple and Filter::Util::Call modules are included in
 the standard distribution), but any decent programmer will be able to
 decrypt it.  You can try using the byte code compiler and interpreter
-described below, but the curious might still be able to de-compile it.
-You can try using the native-code compiler described below, but
-crackers might be able to disassemble it.  These pose varying degrees
-of difficulty to people wanting to get at your code, but none can
-definitively conceal it (true of every language, not just Perl).
+described later in L<perlfaq3>, but the curious might still be able to
+de-compile it. You can try using the native-code compiler described
+later, but crackers might be able to disassemble it.  These pose
+varying degrees of difficulty to people wanting to get at your code,
+but none can definitively conceal it (true of every language, not just
+Perl).
 
 It is very easy to recover the source of Perl programs.  You simply
 feed the program to the perl interpreter and use the modules in

Modified: perlfaq/trunk/perlfaq4.pod
==============================================================================
--- perlfaq/trunk/perlfaq4.pod	(original)
+++ perlfaq/trunk/perlfaq4.pod	Sun Jul  9 05:46:14 2006
@@ -127,11 +127,11 @@
 representations.  This is intended to be representational rather than
 exhaustive.
 
-Some of the examples below use the C<Bit::Vector> module from CPAN.
-The reason you might choose C<Bit::Vector> over the perl built in
-functions is that it works with numbers of ANY size, that it is
-optimized for speed on some operations, and for at least some
-programmers the notation might be familiar.
+Some of the examples later in L<perlfaq4> use the C<Bit::Vector>
+module from CPAN. The reason you might choose C<Bit::Vector> over the
+perl built in functions is that it works with numbers of ANY size,
+that it is optimized for speed on some operations, and for at least
+some programmers the notation might be familiar.
 
 =over 4
 
@@ -1644,7 +1644,7 @@
 To Know" collection in http://www.cpan.org/misc/olddoc/FMTEYEWTK.tgz for
 more about this approach.
 
-See also the question below on sorting hashes.
+See also the question later in L<perlfaq4> on sorting hashes.
 
 =head2 How do I manipulate arrays of bits?
 

Modified: perlfaq/trunk/perlfaq7.pod
==============================================================================
--- perlfaq/trunk/perlfaq7.pod	(original)
+++ perlfaq/trunk/perlfaq7.pod	Sun Jul  9 05:46:14 2006
@@ -312,8 +312,8 @@
 objects.  See L<perlsub/"Pass by Reference"> for this particular
 question, and L<perlref> for information on references.
 
-See "Passing Regexes", below, for information on passing regular
-expressions.
+See "Passing Regexes", later in L<perlfaq7>, for information on
+passing regular expressions.
 
 =over 4
 

Modified: perlfaq/trunk/perlfaq8.pod
==============================================================================
--- perlfaq/trunk/perlfaq8.pod	(original)
+++ perlfaq/trunk/perlfaq8.pod	Sun Jul  9 05:46:14 2006
@@ -437,7 +437,6 @@
 *after* the signal has been caught, rather than while it is being caught.
 Previous versions of this answer were incorrect.
 
-
 =head2 How do I modify the shadow password file on a Unix system?
 
 If perl was installed correctly and your shadow library was written
@@ -487,14 +486,14 @@
 	$done = $start = pack($TIMEVAL_T, ());
 
 	syscall(&SYS_gettimeofday, $start, 0) != -1
-			   or die "gettimeofday: $!";
+		or die "gettimeofday: $!";
 
 	   ##########################
 	   # DO YOUR OPERATION HERE #
 	   ##########################
 
 	syscall( &SYS_gettimeofday, $done, 0) != -1
-		   or die "gettimeofday: $!";
+		or die "gettimeofday: $!";
 
 	@start = unpack($TIMEVAL_T, $start);
 	@done  = unpack($TIMEVAL_T, $done);
@@ -516,7 +515,7 @@
 managed to finish its output without filling up the disk:
 
 	END {
-	    close(STDOUT) || die "stdout close failed: $!";
+		close(STDOUT) || die "stdout close failed: $!";
 	}
 
 The END block isn't called when untrapped signals kill the program,
@@ -808,7 +807,7 @@
 which will get the output quickly (as it is generated, instead of only
 at the end) and also check the return value.
 
-system() also provides direct control over whether shell wildcard
+C<system> also provides direct control over whether shell wildcard
 processing may take place, whereas backticks do not.
 
 =head2 How can I call backticks without shell processing?
@@ -830,13 +829,13 @@
 
 	my @ok = ();
 	if (open(GREP, "-|")) {
-	    while (<GREP>) {
-		chomp;
-		push(@ok, $_);
+		while (<GREP>) {
+			chomp;
+			push(@ok, $_);
 	    }
 	    close GREP;
 	} else {
-	    exec 'grep', @opts, $search_string, @filenames;
+		exec 'grep', @opts, $search_string, @filenames;
 	}
 
 Just as with system(), no shell escapes happen when you exec() a list.
@@ -998,7 +997,7 @@
 
 	if (-t STDIN && -t STDOUT) {
 		print "Now what? ";
-	    }
+		}
 
 On POSIX systems, you can test whether your own process group matches
 the current process group of your controlling terminal as follows: