applied patch (via private mail), modulo retrohunks in pod/perlfaq2.pod

	Subject: Re: docpatch 
	Message-Id: <199807051515.JAA03644@jhereg.perl.com>

p4raw-id: //depot/perl@1325

1 files changed, 13 insertions, 11 deletions

diff --git a/pod/perlfaq4.pod b/pod/perlfaq4.pod
index 8c57db3df0..21daac6fc1 100644
--- a/pod/perlfaq4.pod
+++ b/pod/perlfaq4.pod
@@ -1,6 +1,6 @@
 =head1 NAME
 
-perlfaq4 - Data Manipulation ($Revision: 1.19 $, $Date: 1997/04/24 22:43:57 $)
+perlfaq4 - Data Manipulation ($Revision: 1.24 $, $Date: 1998/07/05 15:07:20 $)
 
 =head1 DESCRIPTION
 
@@ -187,11 +187,12 @@ which should help.
 
 Perl is just as Y2K compliant as your pencil--no more, and no less.
 The date and time functions supplied with perl (gmtime and localtime)
-supply adequate information to determine the year well beyond 2000 (2038
-is when trouble strikes).  The year returned by these functions when used
-in an array context is the year minus 1900.  For years between 1910 and
-1999 this I<happens> to be a 2-digit decimal number. To avoid the year
-2000 problem simply do not treat the year as a 2-digit number.  It isn't.
+supply adequate information to determine the year well beyond 2000
+(2038 is when trouble strikes for 32-bit machines).  The year returned
+by these functions when used in an array context is the year minus 1900.
+For years between 1910 and 1999 this I<happens> to be a 2-digit decimal
+number. To avoid the year 2000 problem simply do not treat the year as
+a 2-digit number.  It isn't.
 
 When gmtime() and localtime() are used in scalar context they return
 a timestamp string that contains a fully-expanded year.  For example,
@@ -256,7 +257,7 @@ For that you'll have to write a parser.
 One destructive, inside-out approach that you might try is to pull
 out the smallest nesting parts one at a time:
 
-    while (s/BEGIN(.*?)END//gs) {
+    while (s//BEGIN((?:(?!BEGIN)(?!END).)*)END/gs) {
 	# do something with $1
     } 
 
@@ -600,7 +601,7 @@ subsequent line.
         return $_;
     }
 
-This owrks with leading special strings, dynamically determined:
+This works with leading special strings, dynamically determined:
 
     $remember_the_main = fix<<'    MAIN_INTERPRETER_LOOP';
 	@@@ int
@@ -659,9 +660,10 @@ ordered and whether you wish to preserve the ordering.
     $prev = 'nonesuch';
     @out = grep($_ ne $prev && ($prev = $_), @in);
 
-This is nice in that it doesn't use much extra memory,
-simulating uniq(1)'s behavior of removing only adjacent
-duplicates.
+This is nice in that it doesn't use much extra memory, simulating
+uniq(1)'s behavior of removing only adjacent duplicates.  It's less
+nice in that it won't work with false values like undef, 0, or "";
+"0 but true" is ok, though.
 
 =item b) If you don't know whether @in is sorted: