From 020fe755c7b9c2c1bba464de4b08e6cb88791d82 Mon Sep 17 00:00:00 2001 From: =?utf8?q?=C3=86var=20Arnfj=C3=B6r=C3=B0=20Bjarmason?= Date: Sun, 17 Oct 2010 13:45:37 -0700 Subject: [PATCH] perldelta entries with tweaks from the committer --- pod/perldelta.pod | 28 ++++++++++++++++++++++------ 1 file changed, 22 insertions(+), 6 deletions(-) diff --git a/pod/perldelta.pod b/pod/perldelta.pod index 9d56fb6..051cf1e 100644 --- a/pod/perldelta.pod +++ b/pod/perldelta.pod @@ -3,9 +3,7 @@ =for comment This has been logged up to 97a3247, except for: -57ef47cc7bcd1b57927d5010f363ccaa10f1d990 b2ea9a00b30eb5881b863d7239dd6a3721e73136 -ca556bcdca736b2f85c11650c70b2371169c0225 e4487e9b537f1be1e95aba1c87790c2a411788a7 68b590d93559da1f7a0d3956202180d507013365 @@ -44,10 +42,13 @@ a C<"(?"> in a regular expression now means that the subexpression is to not inherit the surrounding modifiers such as C, but to revert to the Perl defaults. Any modifiers following the caret override the defaults. -The stringification of regular expressions now uses this notation. The -main purpose of this is to allow tests that rely on the stringification -to not have to change when new modifiers are added. See -L. +The stringification of regular expressions now uses this +notation. E.g., before, C would be stringified as +C<(?i-xsm:hlagh)>, but now it's stringified as C<(?^i:hlagh)>. + +The main purpose of this is to allow tests that rely on the +stringification to not have to change when new modifiers are added. +See L. =head2 C<"d">, C<"l">, and C<"u"> regex modifiers added @@ -830,6 +831,21 @@ The interpreter no longer crashes when freeing deeply-nested arrays of arrays. Hashes have not been fixed yet L<[perl #44225]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=44225>. +=item * + +The mechanism for freeing objects in globs used to leave dangling +pointers to freed SVs, meaning Perl users could see corrupted state +during destruction. + +Perl now only frees the affected slots of the GV, rather than freeing +the GV itself. This makes sure that there are no dangling refs or +corrupted state during destruction. + +=item * + +Perl no longer leaks C or C during +destruction L<[perl #40388]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=40388>. + =back =head1 Known Problems -- 2.7.4