summaryrefslogtreecommitdiff
path: root/pod/perltodo.pod
diff options
context:
space:
mode:
authorNicholas Clark <nick@ccl4.org>2004-07-15 12:47:50 +0000
committerNicholas Clark <nick@ccl4.org>2004-07-15 12:47:50 +0000
commite682d7b7fae5a50c5afb147f913a4e88d7261606 (patch)
tree644c399b397737feec6637e4339926ef7c874e65 /pod/perltodo.pod
parentd46f46af75970be4ecf8811cc8d1ad9bcd7df36c (diff)
downloadperl-e682d7b7fae5a50c5afb147f913a4e88d7261606.tar.gz
for (reverse @foo) now iterates in reverse in place.
p4raw-id: //depot/perl@23115
Diffstat (limited to 'pod/perltodo.pod')
-rw-r--r--pod/perltodo.pod9
1 files changed, 0 insertions, 9 deletions
diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index 156095635c..0c3e8d614a 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -179,15 +179,6 @@ Clean these up. Move them to mathom.c, and don't compile for blead?
The old perltodo notes "This has been done in places, but needs a thorough
code review. Also fchdir is available in some platforms."
-=head2 foreach reverse
-
-The old perltodo notes that we could optimise foreach to iterate in reverse.
-(instead of making a reversed copy on the stack)
-It seems that cx->blk_loop.itermax could be hijacked to act as a go up/go
-down flag, with cx->blk_loop.iterix primed in pp_enteriter for the go down
-case (ie reverse). However, it looks slightly tricky identifying the shape of
-foreach reverse in the optree in Perl_peep.
-
=head1 Tests
=head2 Make Schwern poorer