I posted in SOPW to ask whether I should use a simple output style. You said I should. Fine. But, I disagree with your unspecific comments about chaining GNU tools.

But still a bug. If you're planning on releasing this to CPAN, why not make it as robust as possible?
No. I'll make it as robust as practical and as robust as necessary to be a good module. It's not a module yet, though it's already robust enough to be useful, even before taking the two minutes I'd need to fix the bugs.

You can certainly parse Perl well enough to do what I'm doing, and I've demonstrated that. The proof is in the code, and the code is here.

In reply to Re: Re: Re: Re: Preferred output for development tool by Wassercrats
in thread Preferred output for development tool by Wassercrats

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.