There's always the Orcish Manouvre. Simply keep around a hash of template names and lazily evaluate them if necessary:
my %templates;
# some code
sub include {
my $tpl = shift;
$templates{$tpl} ||= fetch($tpl);
return $tpl;
}
sub fetch {
my $tpl = shift;
local (*TPL, $/);
open(TPL, "template_folder/$tpl") or return;
return <TPL>;
}
It may look very different, and you can get away with
tieing the hash to do lazy lookups. The important point is that, if you have a persistent process that may need to read several files, open them only when necessary and store them all other times.
If your process isn't persistent, then there's not a lot you can do. Open them only when you need to, and pray to the virtual memory subsystem that they stay in cache.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.