Personally, I'd love to see the POD parsers handle some Wiki formatting idioms like the bullet lists.

Any line following a blank line and starting with an asterisk should be seen as an implied =item * instead, using an =over 4 if the preceding paragraph wasn't also a bulleted item.

Any line following such a bullet item and starting with an asterisk should also be seen as an implied =item.

If there is leading whitespace, and the previous line is a bullet item, then inject another =over 4.

To avoid conflict between indented code areas and numbered lists, nested lists have to follow their parents without a blank line. First-column lists can have blank lines above them. Unlike Wiki, you wouldn't need to terminate a list: just start something with less indent or with no asterisk.

An indented line without bullet but immediately following a bulleted line would be seen as a new flowing paragraph at the same indent level, not as the start of a preformatted indented code block.

Same goes for the # for numbered lists; since it's in POD, there's no overlap with Perl comments.

Roughly: 

=head1 METHODS

* new()

  # This is a code block with a Perl comment since
  # it's indented and follows a blank line.
  my $foo = new MyClass(parameters);

Creates a new instance of MyClass.  Valid parameters:
  # --style
    Sets the initial style parameter.  Valid styles:
    * dotted
    * dashed
    * stippled
  # --text
    Sets the initial text parameter.

=cut

[download]

A lot briefer and more readable than the =over4/=item*/=item2 equivalent, I think. And since it can still be expressed AS the above items, maybe it can just be done as a preprocessor step.

--
[ e d @ h a l l e y . c c ]

In reply to Re: •Re: Psuedo-PerlMonk Style Links by halley
in thread Psuedo-PerlMonk Style Links by The Mad Hatter

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.