Because you haven't written a patch for it yet.

At my age one learns to look before one leaps. It may be that it is an intentional design decision, not simply an oversight. I would seem foolish to me to pour a significant volume of time rooting around in a perl's monstrous code base finding the bits to patch, patching them, only then to be told "no, no, we cant do that because of this".

PS: After spending most of last night rooting around in perl's intestinal tract, seem no closer to tacking down where map and grep are implemented. Anyone know off the top of their shaved heads?.

I would seem foolish to me to pour a significant volume of time rooting around in a perl's monstrous code base finding the bits to patch, patching them, only then to be told "no, no, we cant do that because of this".

You could announce your intentions to the committers on the p5p mailing list or on their IRC channel.

no closer to tacking down where map and grep are implemented. Anyone know off the top of their shaved heads?.

$ perl -MO=Concise -e'grep { f() } $x..$y;'
c  <@> leave[1 ref] vKP/REFC ->(end)
1     <0> enter ->2
2     <;> nextstate(main 2 -e:1) v:{ ->3
8     <|> grepwhile(other->9)[t7] vK ->c
7        <@> grepstart K* ->8
3           <0> pushmark s ->4
-           <1> null lK/1 ->4
-              <1> null sK/1 ->8
-                 <@> scope sK ->8
-                    <0> ex-nextstate v ->9
b                    <1> entersub[t2] sKS/TARG,1 ->-
-                       <1> ex-list sK ->b
9                          <0> pushmark s ->a
-                          <1> ex-rv2cv sK ->-
a                             <#> gv[*f] s/EARLYCV ->b
-           <1> null lKM/1 ->7
6              <1> flop lKM ->7
e                 <1> flip[t6] lK ->7
4                    <|> range(other->5)[t5] lK/1 ->d
-                       <1> ex-rv2sv sK/1 ->e
d                          <#> gvsv[*x] s ->e
-                       <1> ex-rv2sv sK/1 ->6
5                          <#> gvsv[*y] s ->6
-e syntax OK
[download]

So pp_grepstart and pp_grepwhile (in pp*.c) for grep. Similarly, map is pp_mapstart and pp_mapwhile.

Keep in mind that the list is already flattened before grep and map see it. First, you'd need to create new ops or use the "S"tacked flag like Perl does for for. (It doesn't appear to be used by the relevant ops.)

$ perl -MO=Concise -e'1 for $x..$y;'
...
8        <{> enteriter(next->9 last->c redo->9) lKS/8 ->a
...                                               ^
                                                  |
                                       Stacked: Is a counting loop

$ perl -MO=Concise -e'1 for (),$x..$y;'
...
9        <{> enteriter(next->a last->d redo->a) lK/8 ->b
...                                               ^
                                                  |
                                     Not Stacked: Is a foreach loop
[download]

Then, you'd need to alter the compiler to produce the right opcode tree when a range is provided.

Update: s/Special/Stacked/

At my age one learns to look before one leaps. It may be that it is an intentional design decision, not simply an oversight.

It's neither an intentional design decision, nor an oversight. In Perl, in general, arguments are evaluated before the sub (or op) is called. So, it's logical that the list is expanded first. It's only later that the case of foreach (x .. y) (but not foreach (x .. y, z) or foreach (z, x .. y)) got optimized as that was a common case, and a lot of memory (and hence, time) could be saved. My guess is that the author who implemented this optimization didn't think the case for grep or map was as pressing - one would expect the result (in list context) of the grep and map to be long lists as well.

Note that I wasn't trying to make a snide remark. People having itches is the main driving force behind Perl.

"no, no, we cant do that because of this".

If your patch doesn't break backwards compatability, and doesn't punish (slowdown, more memory usage, etc) code that doesn't benefit from your patch, there's a good chance it gets accepted. Even if it does contain bugs, isn't perfectly written or causes a problem on some platform you don't have access to, there's a good chance someone else cleans up your effort -- even if it takes a while. Contributions, even if not perfect, are welcomed.

Contributions, even if not perfect, are welcomed.

If only.