summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Guy <mjtg@cam.ac.uk>2004-11-17 18:10:06 +0000
committerNicholas Clark <nick@ccl4.org>2004-11-18 21:15:15 +0000
commit3047bc43d99dde0ccea18f49c67aad54161cfe77 (patch)
tree684c75ab58d3054aeff9597d588cbde80c39c037
parent26fc481e566461861f7455a9d0bdddb267bd2571 (diff)
downloadperl-3047bc43d99dde0ccea18f49c67aad54161cfe77.tar.gz
Re: Proposed patch for perldelta.pod for 5.8.6-RC1
Message-Id: <E1CUUFq-00006L-H7@virgo.cus.cam.ac.uk> Date: Wed, 17 Nov 2004 18:10:06 +0000 p4raw-id: //depot/maint-5.8/perl@23515
-rw-r--r--pod/perl586delta.pod8
1 files changed, 3 insertions, 5 deletions
diff --git a/pod/perl586delta.pod b/pod/perl586delta.pod
index 16182885f7..358e7029b6 100644
--- a/pod/perl586delta.pod
+++ b/pod/perl586delta.pod
@@ -116,11 +116,9 @@ than using the overloaded values. This has been fixed.
C<read> into a UTF8-encoded buffer with an offset off the end of the buffer
no longer mis-calculates buffer lengths.
-There was a long-standing optimization for C<sort {$b cmp $a}> that assumed
-that Perl's C<sort> was not stable. In perl 5.6.x and earlier no guarantee was
-made, so this optimization was valid. 5.8.0 introduced a guarantee of
-stability in the default C<sort> implementation, rendering this optimization
-invalid in specific cases. This has been fixed.
+Although Perl has promised since version 5.8 that C<sort()> would be
+stable, the two cases C<sort {$b cmp $a}> and C<<sort {$b <=> $a}>> could
+produce non-stable sorts. This is corrected in perl5.8.6.
Localising C<$^D> no longer generates a diagnostic message about valid -D
flags.