Document known failures.

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

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index e1d7b18..a0d4472 100644 (file)
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -121,6 +121,10 @@ C<pack('U0a*', ...)> can now be used to force a string to UTF8.
 
 prototype(\&) is now available.
 
+=item *
+
+There is now an UNTIE method.
+
 =back
 
 =head1 Modules and Pragmata
@@ -286,6 +290,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
@@ -738,28 +753,46 @@ The plan is to bring them back.
 
 Certain extensions like mod_perl and BSD::Resource are known to have
 issues with `largefiles', a change brought by Perl 5.6.0 in which file
-offsets default to 64 bits wide where supported.  Modules may fail to
+offsets default to 64 bits wide, where supported.  Modules may fail to
 compile at all or compile and work incorrectly.  Currently there is no
-good solution for the problem, but Configure now stores the relevant
-flags and libraries in the %Config hash so the extensions that are having
-problems can try configuring themselves without the largefileness.
-This is admittedly not a clean solution.
+good solution for the problem, but Configure now provides appropriate
+non-largefile ccflags, ldflags, libswanted, and libs in the %Config
+hash (e.g., $Config{ccflags_nolargefiles}) so the extensions that are
+having problems can try configuring themselves without the
+largefileness.  This is admittedly not a clean solution, and the
+solution may not even work at all.  One potential failure is whether
+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 exposed a flushing bug in VMS, this failure can be ignored.
+
+=head2 Storable tests fail in some platforms
 
 =over 4
 
-=item In string, @%s now must be written as \@%s
+=item *
 
-(F) It used to be that Perl would try to guess whether you wanted an
-array interpolated or a literal @.  It did this when the string was
-first used at runtime.  Now strings are parsed at compile time, and
-ambiguous instances of @ must be disambiguated, either by prepending a
-backslash to indicate a literal, or by declaring (or using) the array
-within the program before the string (lexically).  (I<Someday it will
-simply assume that an unbackslashed @ interpolates an array.>)
+Many Storable tests fail on AIX configured with 64 bit integers.
 
-=back
+So far unidentified problems break Storable in AIX if Perl is
+configured to use 64 bit integers.  AIX in 32-bit mode works and
+other 64-bit platforms work with Storable.
+
+=item *
 
-That day has arrived.
+DOS DJGPP may hang when testing Storable.
+
+=item *
+
+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.
+
+=back
 
 =head1 Reporting Bugs