Well, I also think it's a wheel in need of some re-invention. That's why I'm (in my CFT) reinventing it myself, though I'm aimed in a somewhat different way.

On the POD, it would be nice to say a little more inline with the example in the SYNOPSIS section about what each block is doing. They're reasonably guessable, and hopping back and forth with the long description is good for checking the guesses, but it's documentation; the goal is to not have to guess :)

On the code (or rather the API), one thing I do with my own replacement is to make use of passing args in pairs that can unroll into a hash, in pseudo-named-args fashion. That makes it more readable when you have more than 2 args, and also gives the user more flexibility in arranging things. It also means you can make things explicit instead of implicit (like :flags:, at a glance; I could be wrong about how it works, though).

I can't say I've looked at it terribly in depth; just glanced at the docs and examples. It superficially seems a reasonable tack to take in solving the problems you're aiming at.

In reply to Re: RFC: Module feedback desired. App::PPBuild by fullermd
in thread RFC: Module feedback desired. App::PPBuild by exodist

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.