The expensive recursion can be optimized away. Also, you might also want to specify the "&" prototype to also allow map-like syntax.
sub scanl(&@) { my ($f, @rv) = @_; $rv[$_] = $f->($rv[$_-1], $rv[$_]) for 1..$#rv; return @rv; } my @rv = scanl \&divide, 64, 4,2,4; -or- my @rv = scanl { $_[0] / $_[1] } 64, 4,2,4;

Finally, you could use $a and $b instead of $_[0] and $_[1], but that would prevent the use of existing functions directly. If that's not a problem, using $a and $b can be done by assigning references to *$ap and *$bp after doing

my $pkg = caller(); my $ap = do { no strict 'refs'; \*{$pkg.'::a'} }; local *$ap; my $bp = do { no strict 'refs'; \*{$pkg.'::b'} }; local *$bp;

In reply to Re: functional programming: scan function by ikegami
in thread functional programming: scan function by metaperl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.