You could store all of the documentation in a single file and access it using the core module Pod::Select. The following example reads the NAME POD section from a file and displays it on STDOUT: 
    #!/usr/bin/perl -w

    use strict;
    use Pod::Select;


    my $parser = new Pod::Select();

    $parser->select("NAME");
    $parser->parse_from_file("Module.pm", "-");

    __END__

[download]
However, the POD that is displayed is in raw format without any translation of the POD escapes. So you would probably have to write the data to an intermediary file, or IO::Scalar object, and massage the data.

In the end it may be simpler to create your own selection routine, perhaps via Pod::Parser or Pod::Simple.

--
John.

In reply to Re: perl POD by jmcnamara
in thread perl POD by hotshot

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.