Well, comments... I know that is good to use them to explain the code, but I don't like them, since I think that the programer need to be able to read and understand a code to be a programer.

The only text that I like to make is the POD for the module, explain how to use. But explain why I made some XS like that, etc... not. Is always better read all the code and understand it, and I never read the comments, they are alway bad, or is easier to understand the code.

The best comment that you can make are names that make sence for variables and functions/methods (sub). And of course, use a structure/flux for your code that make sence too.

Graciliano M. P.
"The creativity is the expression of the liberty".

In reply to Re: No Comment by gmpassos
in thread No Comment by awkmonk

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.