summaryrefslogtreecommitdiff
path: root/pod/perl5378delta.pod
diff options
context:
space:
mode:
authorYves Orton <demerphq@gmail.com>2023-02-06 11:03:06 +0100
committerYves Orton <demerphq@gmail.com>2023-02-08 13:03:01 +0800
commit5f5c35d3ce139755d02fa07de26229cd08d3c8cd (patch)
tree2b2d1fb07166852b9fde43dd3cc2c927c88971ae /pod/perl5378delta.pod
parent4202141d20ddfa0501f385cf923860bcf7511398 (diff)
downloadperl-5f5c35d3ce139755d02fa07de26229cd08d3c8cd.tar.gz
regcomp.c - remove (**{ ... }) from the regex engine
Dave M pointed out that this idea was flawed, and after some testing I have come to agree with him. This removes it. It was only available for 5.37.8, so no deprecation cycle involved. The point of (**{ ... }) was to have a postponed eval that does not disable optimizations. But some of the optimizations are disabled because if they are not we do not match correctly as the optimizations will make unwarranted assumptions about the pattern, assumptions which can be incorrect depending on what pattern is returned from the codeblock. The original idea was proposed because (?{ ... }) was treated as though it was (??{ ... }) and disabled many optimizations, when in fact it doesn't interact with optimizations at all. When I added (*{ ... }) as the optimistic version of (?{ ... }) I used "completeness" as the justification for also adding (**{ ... }) when it does not make sense to do so.
Diffstat (limited to 'pod/perl5378delta.pod')
-rw-r--r--pod/perl5378delta.pod3
1 files changed, 3 insertions, 0 deletions
diff --git a/pod/perl5378delta.pod b/pod/perl5378delta.pod
index 980ec09175..ce4f8d3eef 100644
--- a/pod/perl5378delta.pod
+++ b/pod/perl5378delta.pod
@@ -28,6 +28,9 @@ included in a pattern, so that patterns which are O(N) in normal use become
O(N*N) with a C<(?{ ... })> pattern in them. Switching to C<(*{ ... })> means
the pattern will stay O(N).
+B<NOTE> the C<(**{ ... })> was removed in 5.37.9 as it didn't quite work out
+as planned.
+
=head1 Modules and Pragmata
=head2 Updated Modules and Pragmata