Revert #15200 for backwards compatiblity reasons.

[p5sagit/p5-mst-13.2.git] / pod / perl561delta.pod

diff --git a/pod/perl561delta.pod b/pod/perl561delta.pod
index e6c166c..ccd9c8d 100644 (file)
--- a/pod/perl561delta.pod
+++ b/pod/perl561delta.pod
@@ -1,6 +1,6 @@
 =head1 NAME
 
-perldelta - what's new for perl v5.6.x
+perl561delta - what's new for perl v5.6.x
 
 =head1 DESCRIPTION
 
@@ -1052,7 +1052,7 @@ When the last non-weak reference to an object is deleted, the object
 is destroyed and all the weak references to the object are
 automatically undef-ed.
 
-To use this feature, you need the WeakRef package from CPAN, which
+To use this feature, you need the Devel::WeakRef package from CPAN, which
 contains additional documentation.
 
     NOTE: This is an experimental feature.  Details are subject to change.  
@@ -3444,7 +3444,9 @@ is executed:
 
 =over
 
-=item 64-bit builds
+=item 
+
+64-bit builds
 
 Subtest #15 of lib/b.t may fail under 64-bit builds on platforms such
 as HP-UX PA64 and Linux IA64.  The issue is still being investigated.
@@ -3457,21 +3459,27 @@ in 64-bit HP-UX.  The test attempts to create and connect to
 
 Note that 64-bit support is still experimental.
 
-=item Failure of Thread tests
+=item 
+
+Failure of Thread tests
 
 The subtests 19 and 20 of lib/thr5005.t test are known to fail due to
 fundamental problems in the 5.005 threading implementation.  These are
 not new failures--Perl 5.005_0x has the same bugs, but didn't have these
 tests.  (Note that support for 5.005-style threading remains experimental.)
 
-=item NEXTSTEP 3.3 POSIX test failure
+=item
+
+NEXTSTEP 3.3 POSIX test failure
 
 In NEXTSTEP 3.3p2 the implementation of the strftime(3) in the
 operating system libraries is buggy: the %j format numbers the days of
 a month starting from zero, which, while being logical to programmers,
 will cause the subtests 19 to 27 of the lib/posix test may fail.
 
-=item Tru64 (aka Digital UNIX, aka DEC OSF/1) lib/sdbm test failure with gcc
+=item 
+
+Tru64 (aka Digital UNIX, aka DEC OSF/1) lib/sdbm test failure with gcc
 
 If compiled with gcc 2.95 the lib/sdbm test will fail (dump core).
 The cure is to use the vendor cc, it comes with the operating system