perldelta for \$_.\$_ no longer giving 2 addresses

325e181 pad.c: Use &PL_sv_no for const pad names
82b84d0 op.c: Stop copying constants under ithreads
4891fdf pad.c: cast before comparing signed with unsigned
a0ed822 [perl #78194] Make grep/map copy pad tmps
b479c9f [perl #78194] Make sub calls copy pad tmps
8e079c2 [perl #78194] Make foreach copy pad tmps
706a6eb [perl #78194] Make list slices copy PADTMPs in lv cx
da9e430 [perl #78194] Make x copy PADTMPs in lv cx
2b66f6d [perl #78194] Make sort copy PADTMPs
82c2360 [perl #78194] Make re-evals copy PADTMPs
fb09017 pad.c apidocs: Clarify use of &PL_sv_no

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index becd10d..1c07a51 100644 (file)
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -460,6 +460,15 @@ that had had a glob assigned to it.  This has been fixed [perl #119051].
 On 64-bit platforms C<pos> can now be set to a value higher than 2**31-1
 [perl #72766].
 
+=item *
+
+Perl used to leak an implementation detail when it came to referencing the
+return values of certain operators.  C<for ($a+$b) { warn \$_; warn \$_ }>
+used to display two different memory addresses, because the C<\> operator
+was copying the variable.  Under threaded builds, it would also happen for
+constants (C<for(1) { ... }>).  This has been fixed [perl #21979, #78194,
+#89188, #109746, #114838, #115388].
+
 =back
 
 =head1 Known Problems