Or differences in compilers and flags used to build the versions.

$ perl -v | grep ^This
This is perl, v5.8.3 built for i486-linux
$ perl -V:gccversion
gccversion='3.3.2';
$ perl -V:config_args
config_args='-de -Dprefix=/usr -Dcccdlflags=-fPIC -Dinstallprefix=/usr
+ -Doptimize=-O3 -march=i486 -mcpu=i686 -Darchname=i486-linux';

[download]

The relevant bits for call context are in the runloop() function:

    # ...
    if (ref $c eq 'CODE') {
    $subcode = "sub { for (1 .. $n) { local \$_; package $pack; &\$c; 
+} }";
        $subref  = eval $subcode;
    }
    else {
    $subcode = "sub { for (1 .. $n) { local \$_; package $pack; $c;} }
+";
        $subref  = _doeval($subcode);
    }
    # ...
    &$subref;

[download]

(_doeval is basically a eval.)

So void context, but I don't think that matters here — the compiler doesn't know the context at the time of eval, so shouldn't be optimizing things away. One would have to instrument the code with a few B::Deparse calls to know for sure, of course. But going by the numbers from the benchmark, it doesn't seem to be making the difference.

There just seems to be a high startup overhead for first that amortizes over time, given enough time, for at least some Perls.

Makeshifts last the longest.

In reply to Re^17: Specializing Functions with Currying by Aristotle
in thread Specializing Functions with Currying by FoxtrotUniform

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.