Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • ... but I basically agree. I only write long comments (that is, sentences instead of short phrases) when it is to discuss why the code is doing what it is doing, rather than discussing what it is doing; or, if what it is doing is really really weird, and I want to explain it to myself (or someone else) later on. The latter case is quite rare, and I cannot recall an example of it offhand. The former case happens once or twice a month, maybe.

    Most of my comments are just quick labels saying what something
    • Oh yeah? I've blown sweeter notes out of my ass-aphone!

      I'm in agreement with your clarifications, Pudge-daddy. Once again, you have crystalized my thoughts eloquently.

  • I've kind of fallen into an odd trap. I comment the hell out of the space *just before* something, and then I put little comments in when I figure it's not clear what's where and where's what.

    That is, I explain what's supposed to be going on (mainly to myself so I'll remember later) and then, if the code is particularly long or arduous or uses lots of functions I don't understand, I comment specific lines. I try to avoid that, though.

    Of course, this is code for *me*, at this point. When I get it clea

    --

    ------------------------------
    You are what you think.