Am I reading this right, or ignoring something obvious?
That is the way I read it as well.
I took a look at installman , here are some ideas I had for making it faster
Rewrite it so it doesn't use no_chdir, because that is supposed to be slower
File::Find::find({no_chdir=>1,
You can also get rid of this stat (-f), because there are no directories in perl/lib or perl/pod , that end in .pm or .pod
if (-f $_ and /\.p(?:m|od)$/) {
Hmm, actually, you might be able to get rid of File::Find altogether by caching the file list perl\pod\buildtoc generates
But, I doubt you could make a significant dent in the runtime with these simple ideas (I guesstimate 10 seconds), due to OS level file system caching .
What would probably work better is making Pod::Man->new happen in a few threads
Oh, and I didn't even look at Pod::Simple::BlackBox :)
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.