Ah, good. I didn't know about the -l switch. But really, I wanted to avoid making a call to an external program to translate the filename (though I suppose that's a lot better than what I was doing (opening a pipe to perldoc -m Module to read the file in) and it would be more robust than what I have).

Well, putting aside for the moment the fact that I'm reinventing a little wheel, I'd like to know what everyone thinks about my implementation. Is there anything I'm missing that would cause this to choke? Am I totally going about it wrong? Or does it look Ok?

bbfu
Seasons don't fear The Reaper.
Nor do the wind, the sun, and the rain.
We can be like they are.

In reply to (bbfu) (perldoc -l) Re: Re: Translating Module Names to File Names by bbfu
in thread Translating Module Names to File Names by bbfu

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.