Re: [PATCH perl@6962] 2 more vms.c fix-ups and status

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

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index d739204..f3608e9 100644 (file)
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -160,8 +160,9 @@ the podlators bundle, Pod::LaTeX, Pod::Parser, Term::ANSIColor, Test.
 
 Bug fixes and minor enhancements have been applied to B::Deparse,
 Data::Dumper, IO::Poll, IO::Socket::INET, Math::BigFloat,
-Math::Complex, Math::Trig, Net::protoent, re, SelfLoader, Sys::SysLog,
-Test::Harness, Text::Wrap, UNIVERSAL.
+Math::Complex, Math::Trig, Net::protoent, the re pragma, SelfLoader,
+Sys::SysLog, Test::Harness, Text::Wrap, UNIVERSAL, and the warnings
+pragma.
 
 =item *
 
@@ -210,6 +211,8 @@ C<%INC> now localised in a Safe compartment so that use/require work.
 
 The Shell module now has an OO interface.
 
+=item *
+
 =back
 
 =head1 Utility Changes
@@ -290,6 +293,17 @@ distribution.
 
 map() that changes the size of the list should now work faster.
 
+=item *
+ 
+sort() has been changed to use mergesort internally as opposed to the
+earlier quicksort.  For very small lists this may result in slightly
+slower sorting times, but in general the speedup should be at least 20%.
+Additional bonuses are that the worst case behaviour of sort() is now
+better (in computer science terms it now runs in time O(N log N), as
+opposed to quicksorts Theta(N**2) worst-case run time behaviour), and
+that sort() is now stable (meaning that elements with identical keys
+will stay ordered as they were before the sort).
+
 =back
 
 =head1 Installation and Configuration Improvements
@@ -754,11 +768,6 @@ one can (or, if one can, whether it's a good idea) link together at
 all binaries with different ideas about file offsets, all this is
 platform-dependent.
 
-=head2 ftmp-posix subtest 6 fails in VMS
-
-The test exposes a flushing bug in the VMS port of Perl, this failure
-as such can be ignored.
-
 =head2 ftmp-security tests warn 'system possibly insecure'
 
 Don't panic.  Read INSTALL 'make test' section instead. 
@@ -766,10 +775,13 @@ Don't panic.  Read INSTALL 'make test' section instead.
 =head2 Long Doubles Still Don't Work In Solaris
 
 The experimental long double support is still very much so in Solaris.
-(Other platforms like Linux and Tru64 are beginning to solidify in this area.)
+(Other platforms like Linux and Tru64 are beginning to solidify in
+this area.)
 
 =head2 Storable tests fail in some platforms
 
+If any Storable tests fail the use of Storable is not advisable.
+
 =over 4
 
 =item *
@@ -791,6 +803,39 @@ st-06compat fails in UNICOS and UNICOS/mk.
 This means that you cannot read old (pre-Storable-0.7) Storable images
 made in other platforms.
 
+=item *
+
+st-store.t and st-retrieve may fail with Compaq C 6.2 on OpenVMS Alpha 7.2.
+
+=head2 Threads Are Still Experimental
+
+Multithreading is still an experimental feature.  Some platforms
+emit the following message for lib/thr5005
+
+    #
+    # This is a KNOWN FAILURE, and one of the reasons why threading
+    # is still an experimental feature.  It is here to stop people
+    # from deploying threads in production. ;-)
+    #
+ 
+and another known warning is
+
+   pragma/overload......Unbalanced saves: 3 more saves than restores
+   panic: magic_mutexfree during global destruction.
+   ok
+   lib/selfloader.......Unbalanced saves: 3 more saves than restores
+   panic: magic_mutexfree during global destruction.
+   ok
+   lib/st-dclone........Unbalanced saves: 3 more saves than restores
+   panic: magic_mutexfree during global destruction.
+   ok
+
+=head2 The Compiler Suite Is Still Experimental
+
+The compiler suite is slowly getting better but is nowhere near yet.
+The backend part that has seen perhaps the most progress is the
+bytecode compiler.
+
 =back
 
 =head1 Reporting Bugs