[inseparable changes from match from perl-5.003_94 to perl-5.003_95]

 CORE LANGUAGE CHANGES

Subject: Don't compile scalar mods of aggregates, like C<@a =~ s/a/b/>
From: Chip Salzenberg <chip@perl.com>
Files: op.c t/op/misc.t

Subject: Warn about undef magic values just like non-magic
From: Chip Salzenberg <chip@perl.com>
Files: ext/Opcode/Safe.pm sv.c t/lib/db-btree.t t/lib/db-hash.t t/lib/db-recno.t t/pragma/locale.t

 CORE PORTABILITY

Subject: Win32 update (five patches)
From: Gurusamy Sarathy <gsar@engin.umich.edu>
Files: MANIFEST README.win32 doio.c dosish.h pp_sys.c lib/ExtUtils/Command.pm t/comp/multiline.t t/op/magic.t t/op/mkdir.t t/op/runlevel.t t/op/stat.t t/op/write.t win32/Makefile win32/config.H win32/config.w32 win32/win32.c win32/win32.h win32/win32aux.c win32/*.mak win32/VC-2.0/*.mak

 DOCUMENTATION

Subject: INSTALL-1.8 to INSTALL-1.9 updates
Date: Tue, 25 Mar 1997 13:52:53 -0500 (EST)
From: Andy Dougherty <doughera@fractal.phys.lafayette.edu>
Files: INSTALL
Msg-ID: Pine.SOL.3.95q.970325135138.3374A-100000@fractal.lafayette.e

    (applied based on p5p patch as commit 9b1ae96a0b4301a9588f62b3175bc0312302f4b9)

Subject: Document possible problems with -Mdiagnostics after upgrade
From: Chip Salzenberg <chip@perl.com>
Files: INSTALL

Subject: Mention perldelta in INSTALL
From: Chip Salzenberg <chip@perl.com>
Files: INSTALL

Subject: Describe pod format at top of INSTALL
From: Chip Salzenberg <chip@perl.com>
Files: INSTALL

Subject: Document C</a *b/x> fix
From: Chip Salzenberg <chip@perl.com>
Files: pod/perldelta.pod

Subject: pods for subroutine argument autovivication
Date: Mon, 24 Mar 1997 07:25:21 +0000
From: "M.J.T. Guy" <mjtg@cus.cam.ac.uk>
Files: pod/perldelta.pod pod/perlsub.pod
Msg-ID: E0w9489-0005YT-00@ursa.cus.cam.ac.uk

    (applied based on p5p patch as commit db8878faa51a8a1541a40745a8613adb5db155e4)

Subject: Missing item in perldiag
Date: Sun, 23 Mar 1997 09:24:09 +0000
From: "M.J.T. Guy" <mjtg@cus.cam.ac.uk>
Files: pod/perldiag.pod
Msg-ID: E0w8jVZ-0005va-00@ursa.cus.cam.ac.uk

    (applied based on p5p patch as commit c00a529017138505fcbe538b74c7884abe1d18e1)

Subject: Pod problems & fixes
Date: Mon, 24 Mar 1997 21:31:51 +0100 (MET)
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Files: INSTALL lib/Term/Complete.pm lib/subs.pm pod/perlcall.pod pod/perldata.pod pod/perldiag.pod pod/perlembed.pod pod/perlguts.pod pod/perlmod.pod pod/perlop.pod pod/perlpod.pod pod/pod2html.PL
Msg-ID: 199703242031.VAA14997@bombur2.uio.no

    (applied based on p5p patch as commit 55a864fe4cea1a0586891b83d359ba71e0972da5)

Subject: FAQ update
From: Nathan Torkington <gnat@prometheus.frii.com>
Files: pod/perlfaq*.pod

 OTHER CORE CHANGES

Subject: Improve 'prototype mismatch' warning
From: Chip Salzenberg <chip@perl.com>
Files: global.sym op.c pod/perldiag.pod proto.h sv.c t/comp/redef.t

1 files changed, 10 insertions, 20 deletions

diff --git a/README.win32 b/README.win32
index 36953ec0da..82c9bacfab 100644
--- a/README.win32
+++ b/README.win32
@@ -13,12 +13,12 @@ These are instructions for building Perl under WindowsNT (versions
 
 =head1 DESCRIPTION
 
-Before you start, you should glance through the README file found
+Before you start, you should glance through the README file
 found in the top-level directory where the Perl distribution
 was extracted.  Make sure you read and understand the terms under
 which this software is being distributed.
 
-Make sure you read the L<BUGS AND CAVEATS> section below for the
+Also make sure you read the L<BUGS AND CAVEATS> section below for the
 known limitations of this port.
 
 The INSTALL file in the perl top-level has much information that is
@@ -76,8 +76,8 @@ but it doesn't hurt to do so.
 
 The "win32" directory contains *.mak files for use with the NMAKE that
 comes with Visual C++ ver. 4.0 and above.  If you wish to build perl
-using Visual C++ versions between 2.0 and 4.0, do the following three
-additional steps (these three steps are not required if you are
+using Visual C++ versions between 2.0 and 4.0, do the following two
+additional steps (these steps are not required if you are
 using Visual C++ versions 4.0 and above):
 
 =over 8
@@ -85,9 +85,7 @@ using Visual C++ versions 4.0 and above):
 =item 1.
 
 Overwrite the *.mak files in the win32 subdirectory with the versions
-in the win32\VC-2.0 directory.  (The only difference in those makefiles
-is in how the $(INCLUDE) variable is handled--VC 2.0 NMAKE does not
-grok a path list in $(INCLUDE)).
+in the win32\VC-2.0 directory.
 
 =item 2.
 
@@ -100,15 +98,6 @@ This must have only one directory (a list of directories will not work).
 VCVARS32.BAT may put multiple locations in there, which is why this step
 is required.
 
-=item 3.
-
-Apply the patch found in win32\VC-2.0\vc2.patch, like so:
-
-	cd win32
-	patch -p2 -N < VC-2.0\vc2.patch
-
-You may have to edit win32\win32.c manually if you don't have GNU patch.
-
 =back
 
 =item * 
@@ -152,16 +141,17 @@ This should produce a summary very similar to the following:
     Failed Test  Status Wstat Total Fail  Failed  List of failed
     ------------------------------------------------------------------------------
     io/fs.t                      26   16  61.54%  1-5, 7-11, 16-18, 23-25
-    io/tell.t                    13    1   7.69%  10
     lib/anydbm.t                 12    1   8.33%  2
     lib/findbin.t                 1    1 100.00%  1
     lib/sdbm.t                   12    1   8.33%  2
+    op/magic.t                   28    1   3.57%  16
     op/mkdir.t                    7    2  28.57%  3, 7
     op/runlevel.t                 8    1  12.50%  4
-    op/stat.t                    56    3   5.36%  3-4, 20
+    op/stat.t                    56    3   5.36%  2-3, 20
     op/taint.t                   98   20  20.41%  1-6, 14, 16, 19-21, 24, 26, 35-3
     pragma/locale.t              98   40  40.82%  1, 13-14, 21-27, 33, 39, 45-53,
-    Failed 10/149 test scripts, 93.29% okay. 86/3506 subtests failed, 97.55% okay.
+    Failed 10/149 test scripts, 93.29% okay. 86/3871 subtests failed, 97.78% okay.
+
 
 Check if any additional tests other than the ones shown here
 failed.  The standard testsuite will ultimately be modified so
@@ -173,7 +163,7 @@ This is still very much an experimental port, and should be considered
 alpha quality software.  You can expect changes in virtually all of
 these areas: build process, installation structure, supported
 utilities/modules, and supported perl functionality.  Specifically,
-functionality that supports the Win32 environment may be ultimately
+functionality that supports the Win32 environment may ultimately
 be supported as either core modules or extensions.
 
 Many tests from the standard testsuite either fail or produce different