The thing to remember is that Pod parsers don't execute code. Pod and Perl are just two languages that can live in the same file and each parser just ignores the other language. So you can't use Perl constructs or source filters to affect how Pod parsers see the file.

However, you might be able to take advantage of the fact that perldoc will prefer a .pod file to a .pm file. For an example of how that could work, consider Pod::WikiDoc.

Pod::WikiDoc parses a .pm file containing "wikidoc" Pod format blocks when the distribution tarball is created and creates a matching .pod file with the wikidoc blocks converted to Pod. On installation, the .pod are what perldoc finds and end-users never need to know or care that I used Pod::WikiDoc to write my Pod.

You could do something similar where some template Pod format block gets expanded into a separate .pod file. You just need to customize a Pod parser to pre-process the .pm file, process your templates, and stick the results into a .pod file.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

In reply to Re: Templating pod generation? by xdg
in thread Templating pod generation? by diotalevi

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.