I have needed both these features, and add my vote to both your suggestions. Regarding Suggestion 1, Pod::Usage is an excellent solution where it's relevant, but it only covers a narrow set of cases. There are many cases where information needs to be in both code and documentation, especially version related information.

I've also needed your Suggestion 2. I try to make documentation convenient for whoever will maintain the module (and so make it more likely to be maintained), and to make it readable for those who use the module. It's often tough to put code in the module, in the right place to make the user documentation come out the way it should.

In reply to Re: pod6 --- code+pod suggestion by rodion
in thread pod6 --- code+pod suggestion by iaw4

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.