summaryrefslogtreecommitdiff
path: root/regen
diff options
context:
space:
mode:
authorFather Chrysostomos <sprout@cpan.org>2012-04-21 23:28:51 -0700
committerFather Chrysostomos <sprout@cpan.org>2012-05-21 16:51:28 -0700
commit3404114d245bcf6ac70053764a86a30617239aa9 (patch)
tree5f3be86cb9fad47c007f33ec6b47948eddad5733 /regen
parentde290e1f6850f9240f165cc786940b0ff682718b (diff)
downloadperl-3404114d245bcf6ac70053764a86a30617239aa9.tar.gz
regen/opcodes: Rmv evalonce comment
This goes all the way back to when perl 5.0 was being polished up. The idea behind evalonce is that eval "constant string" should be optimisable by being compiled ahead of time, just like eval { ... }. But this could never work properly, because BEGIN blocks would only fire once. Also, eval '$x .. $y' is an easy way to create two separ- ate flip-flops. There are undoubtedly many other reasons why this could never work. So there is no reason to keep this comment any longer, as it is not (or should not be) a to-do item.
Diffstat (limited to 'regen')
-rw-r--r--regen/opcodes1
1 files changed, 0 insertions, 1 deletions
diff --git a/regen/opcodes b/regen/opcodes
index 22cc9133fd..0beba6a90d 100644
--- a/regen/opcodes
+++ b/regen/opcodes
@@ -485,7 +485,6 @@ dofile do "file" ck_fun d1 S
hintseval eval hints ck_svconst s$
entereval eval "string" ck_eval du% S?
leaveeval eval "string" exit ck_null 1 S
-#evalonce eval constant string ck_null d1 S
entertry eval {block} ck_eval d|
leavetry eval {block} exit ck_null @