No, that won’t work. Generally, you have to generate your POD statically, else it won’t be understood by POD processors. So why not document them all once, instead of repetitively documenting each with the same boilerplate?

=head2 io( OBJ )

=head2 fm( OBJ )

=head2 cv( OBJ )

=head2 hv( OBJ )

=head2 pvlv( OBJ )

=head2 gv( OBJ )

=head2 av( OBJ )

=head2 bm( OBJ )

=head2 pvmg( OBJ )

=head2 pvnv( OBJ )

=head2 pviv( OBJ )

=head2 rv( OBJ )

=head2 nv( OBJ )

=head2 iv( OBJ )

=head2 pv( OBJ )

=head2 sv( OBJ )

Returns a boolean indicating whether OBJ is an instance of the B:: cla
+ss indicated by the method name, and respects any overridden C<-E<gt>
+isa> methods.

[download]

Granted, that’s not entirely DRY. For that, you could try turning your question on its head by parsing your own POD at load time in order to get the list of functions to generate. (I also enjoy Pod::Constants, but it doesn’t fit your use case.)

PS.: your use of eval is unnecessary:

for my $nm ( qw( io fm cv hv pvlv gv av bm pvmg pvnv pviv rv nv iv pv 
+sv ) ) {
    my $nm_pkg = "B::$nm";
    *{ $nm } = sub {
        my $op = shift @_;
        return blessed( $op ) and $op->isa( $nm_pkg );
    }
}

[download]

Makeshifts last the longest.

In reply to Re: Templating pod generation? by Aristotle
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.