Several people have pointed out that "only perl can parse Perl".

This is an epigram, a play on words, a joke. It isn't an axiom unless we treat it as such.

Perltidy parses perl well enough for most peoples requirements. Also, Damian Conway has stated many times that he wants to parse Perl in Perl. As far as I've seen he doesn't get this type of reaction.

Adam's goal of parsing 99.9% of Perl, or at least the Perl on CPAN, is worthy and possibly obtainable. He appears to be aware of the difficulties. As such we such lend support rather than prejudging it. A tool such as this would be extremely useful. The CPANTS project, for instance, is probably doomed without something like this.

--
John.

In reply to Re: Appropriate CPAN namespace for perl parser by jmcnamara
in thread Appropriate CPAN namespace for perl parser by Anonymous Monk

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.