Like everyone else, I doubt that there is any speed saving. do() is like scalar eval `cat filename` according to perldoc and this leads me to believe that, while compile time may be quicker, runtime will actually be slower due to the overheads needed to set up the sub call. However, there are some obscure advantages to this method; I wrote a program a little while ago that called blocks of perl code from a database upon demand and eval'd them. This was slow and hard to debug but allowed large parts of the program to be edited at runtime.

$japh->{'Caillte'} = $me;

In reply to Re: Saving compile time by running subroutines as separate files with 'do' by Caillte
in thread Saving compile time by running subroutines as separate files with 'do' by George_Sherston

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.