> I'm sure compilation speed shouldn't matter when generating closures. (I will add a benchmark later this day)

Here a simplified example which showed that installing subs with closures¹ is 5 times faster than eval.

That's less dramatic than I thought, but eval performance also heavily depends on the length of code.

So adding 10 no-ops already made eval 10 times slower while closure didn't change.

use strict;
use warnings;
use Time::HiRes qw/time/;


BEGIN {
    $\="\n";
    my $count=1000;
    sub noop { };
    
    my $start=time;
    sub tag_gen {
        my ($tag)=@_;
        sub {
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            "<$tag>",@_,"</$tag>";
        }
    }
    {
        no strict 'refs';
        for my $x (1..$count) {
            
            my $tag="h$x";
            *{$tag}=tag_gen($tag);
        }
    }
    print "Closure: ",time-$start;

    
    $start = time;
    for my $x (1..$count) {
        my $tag="H$x";
        eval sprintf <<'__CODE__', $tag;
        sub %1$s {
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");
            noop("Ipse Lorum");

            "<%1$s>",@_,"</%1$s>";
        }
__CODE__
    }
    print "Eval: ",time-$start;
}





print h1 h2 "closure";

print H1 H2 "eval";

[download]

output: 

Closure: 0.0279860496520996
Eval: 0.343567132949829
<h1><h2>closure</h2></h1>
<H1><H2>eval</H2></H1>

[download]

One has to keep in mind that 15-20 years ago machines were factor 1000 slower, i.e. auto loading was relevant.

Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)

PS: Je suis Charlie!

update

fixed bug with no-ops.

¹) currying to be precise

In reply to Re^7: Removing AUTOLOAD from CGI.pm (closure vs eval) by LanX
in thread Removing AUTOLOAD from CGI.pm by leej

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.