[inseparable changes from match from perl-5.003_97c to perl-5.003_97d]perl-5.003_97d

 DOCUMENTATION

Subject: more (err, less) doubled words
Date: Fri, 11 Apr 1997 22:31:25 +0300 (EET DST)
From: Jarkko Hietaniemi <Jarkko.Hietaniemi@cc.hut.fi>
Files: ext/DB_File/DB_File.pm ext/DynaLoader/DynaLoader.pm ext/IO/lib/IO/Pipe.pm lib/CGI.pm lib/Exporter.pm lib/ExtUtils/MakeMaker.pm lib/IPC/Open2.pm lib/IPC/Open3.pm lib/vars.pm pod/perlcall.pod pod/perldiag.pod pod/perlfaq1.pod pod/perlfaq3.pod pod/perlfaq5.pod pod/perlfaq7.pod pod/perlfaq8.pod pod/perlipc.pod

    private-msgid: 199704111931.WAA24460@alpha.hut.fi

 LIBRARY AND EXTENSIONS

Subject: win32: perl5db patch
Date: Thu, 10 Apr 1997 17:42:13 -0400
From: Gurusamy Sarathy <gsar@engin.umich.edu>
Files: lib/perl5db.pl
Msg-ID: 199704102142.RAA27396@aatma.engin.umich.edu

    (applied based on p5p patch as commit 56cbacacb6c634a626b06407cbd555bc1519a2d5)

Subject: Enhancements to debugger, Term::ReadLine, Term::Cap
Date: Thu, 10 Apr 1997 15:48:07 -0400 (EDT)
From: Ilya Zakharevich <ilya@math.ohio-state.edu>
Files: lib/Term/Cap.pm lib/Term/ReadLine.pm lib/perl5db.pl
Msg-ID: 199704101948.PAA01841@monk.mps.ohio-state.edu

    (applied based on p5p patch as commit 6fb2d361298c4eb5d42f1f63b0f74a60d407e546)

 OTHER CORE CHANGES

Subject: New error msg for low-key failure of C<require>
From: Chip Salzenberg <chip@perl.com>
Files: pod/perldiag.pod pp_ctl.c t/pragma/strict-subs t/pragma/strict-vars

9 files changed, 19 insertions, 13 deletions

diff --git a/pod/perlcall.pod b/pod/perlcall.pod
index 85e0237827..5a689d0304 100644
--- a/pod/perlcall.pod
+++ b/pod/perlcall.pod
@@ -356,7 +356,7 @@ As mentioned above, you can determine the context of the currently
 executing subroutine in Perl with I<wantarray>.  The equivalent test
 can be made in C by using the C<GIMME_V> macro, which returns
 C<G_ARRAY> if you have been called in an array context, C<G_SCALAR> if
-in a a scalar context, or C<G_VOID> if in a void context (i.e. the
+in a scalar context, or C<G_VOID> if in a void context (i.e. the
 return value will not be used).  An older version of this macro is
 called C<GIMME>; in a void context it returns C<G_SCALAR> instead of
 C<G_VOID>.  An example of using the C<GIMME_V> macro is shown in
diff --git a/pod/perldiag.pod b/pod/perldiag.pod
index cdc7c59c1a..080c2a76d7 100644
--- a/pod/perldiag.pod
+++ b/pod/perldiag.pod
@@ -613,7 +613,7 @@ package name.
 
 =item Can't locate %s in @INC
 
-(F) You said to do (or require, or use) a file that couldn't be found in
+(F) You said to do (or require, or use) a file that couldn't be found
 in any of the libraries mentioned in @INC.  Perhaps you need to set the
 PERL5LIB or PERL5OPT environment variable to say where the extra library
 is, or maybe the script needs to add the library name to @INC.  Or maybe
@@ -842,6 +842,12 @@ to 01411.  Octal constants are introduced with a leading 0 in Perl, as in C.
 
 (W) You tried to close a filehandle that was never opened.
 
+=item Compilation failed in require
+
+(F) Perl could not compile a file specified in a C<require> statement.
+Perl uses this generic message when none of the errors that it encountered
+were severe enough to halt compilation immediately.
+
 =item connect() on closed fd
 
 (W) You tried to do a connect on a closed socket.  Did you forget to check
diff --git a/pod/perlfaq1.pod b/pod/perlfaq1.pod
index 5d45c819c5..99d4b35bee 100644
--- a/pod/perlfaq1.pod
+++ b/pod/perlfaq1.pod
@@ -187,7 +187,7 @@ ok, while "awk and Perl" and "Python and perl" do not.
 It doesn't matter.
 
 In "standard terminology" a I<program> has been compiled to physical
-machine code once, and can then be be run multiple times, whereas a
+machine code once, and can then be run multiple times, whereas a
 I<script> must be translated by a program each time it's used.  Perl
 programs, however, are usually neither strictly compiled nor strictly
 interpreted.  They can be compiled to a bytecode form (something of a Perl
diff --git a/pod/perlfaq3.pod b/pod/perlfaq3.pod
index af7e53b8fe..e6bfd3de73 100644
--- a/pod/perlfaq3.pod
+++ b/pod/perlfaq3.pod
@@ -351,7 +351,7 @@ interpreter.  If you install another port, or (eventually) build your
 own Win95/NT Perl using WinGCC, then you'll have to modify the
 Registry yourself.
 
-Macintosh perl scripts will have the the appropriate Creator and
+Macintosh perl scripts will have the appropriate Creator and
 Type, so that double-clicking them will invoke the perl application.
 
 I<IMPORTANT!>: Whatever you do, PLEASE don't get frustrated, and just
diff --git a/pod/perlfaq5.pod b/pod/perlfaq5.pod
index 47c6dead22..1c694f0347 100644
--- a/pod/perlfaq5.pod
+++ b/pod/perlfaq5.pod
@@ -406,8 +406,8 @@ atomic test-and-set instruction.   In theory, this "ought" to work:
 
 except that lamentably, file creation (and deletion) is not atomic
 over NFS, so this won't work (at least, not every time) over the net.
-Various schemes involving involving link() have been suggested, but
-these tend to involve busy-wait, which is also subdesirable.
+Various schemes involving link() have been suggested, but these tend
+to involve busy-wait, which is also subdesirable.
 
 =head2 I still don't get locking.  I just want to increment the number
 in the file.  How can I do this?
diff --git a/pod/perlfaq7.pod b/pod/perlfaq7.pod
index 1047b28634..a1d60f84d5 100644
--- a/pod/perlfaq7.pod
+++ b/pod/perlfaq7.pod
@@ -339,9 +339,9 @@ IO::File modules, both part of the standard Perl distribution.
 
 To pass regexps around, you'll need to either use one of the highly
 experimental regular expression modules from CPAN (Nick Ing-Simmons's
-Regexp or Ilya Zakharevich's Devel::Regexp), pass around strings
-and use an exception-trapping eval, or else be be very, very clever.
-Here's an example of how to pass in a string to be regexp compared:
+Regexp or Ilya Zakharevich's Devel::Regexp), pass around strings and
+use an exception-trapping eval, or else be very, very clever.  Here's
+an example of how to pass in a string to be regexp compared:
 
     sub compare($$) {
         my ($val1, $regexp) = @_;
diff --git a/pod/perlfaq8.pod b/pod/perlfaq8.pod
index fba9a249aa..831b1b41e7 100644
--- a/pod/perlfaq8.pod
+++ b/pod/perlfaq8.pod
@@ -619,7 +619,7 @@ module for other solutions.
 
 =item *
 
-Open /dev/tty and use the the TIOCNOTTY ioctl on it.  See L<tty(4)>
+Open /dev/tty and use the TIOCNOTTY ioctl on it.  See L<tty(4)>
 for details.
 
 =item *
diff --git a/pod/perlipc.pod b/pod/perlipc.pod
index 86dda59137..12b6b918ca 100644
--- a/pod/perlipc.pod
+++ b/pod/perlipc.pod
@@ -289,7 +289,7 @@ should check their Your_OS::Process module for other solutions.
 
 =item *
 
-Open /dev/tty and use the the TIOCNOTTY ioctl on it.  See L<tty(4)>
+Open /dev/tty and use the TIOCNOTTY ioctl on it.  See L<tty(4)>
 for details.
 
 =item *
diff --git a/pod/perltoc.pod b/pod/perltoc.pod
index ae5f768c47..858d783ea2 100644
--- a/pod/perltoc.pod
+++ b/pod/perltoc.pod
@@ -861,8 +861,8 @@ $^E, $^H, $^M
 
 delete on slices, flock, printf and sprintf, keys as an lvalue, my() in
 Control Structures, unpack() and pack(), use VERSION, use Module VERSION
-LIST, prototype(FUNCTION), srand, $_ as Default, C<m//g> does not trigger a
-pos() reset on failure, C<m//x> ignores whitespace before ?*+{}, nested
+LIST, prototype(FUNCTION), srand, $_ as Default, C<m//g> does not reset
+search position on failure, C<m//x> ignores whitespace before ?*+{}, nested
 C<sub{}> closures work now, formats work right on changing lexicals
 
 =item New builtin methods