I can see the need for development standards and comments.. In fact we have standards that require a comment block at the top of each file, and before each function, explaining what it is, which project it belongs to, who wrote it, etc. Nothing wrong with that at all. Tho having said that, I don't see much point in extracting comments without the code they're supposed to annotate.

Whatever, you'll probably need a code parser to extract *just* the comments, pretty difficult as in perl the quote operators can use almost anything as delimiters, you'd actually have to check for keywords etc. Parse::RecDescent maybe? (Sounds crazy though) - Or just update Regexp::Common::comment your own Regexes?

C.

In reply to Re: Extracting Comments by castaway
in thread Extracting Comments by nofernandes

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.