<!-- Discuss how written instructions need to be done to be clear. --> Written language needs to be terse to be clear. <!-- Duplication is bad --> Duplicating ideas or needlessly repeating concepts or even exact language does not clarify. <!-- Duplication muddies. --> It muddies.

<!-- What about programming? --> This is especially true in programming. <!-- Clarify why. --> A program is a set of instructions. Needless division and duplication in instructions is obviously a problem. The hacker reading the code is parsing it in his <!-- Be gender neutral. --> or her head. With clear, well modularized code this isn't hard for a good hacker but it requires focus. <!-- It can be made hard though. Here's how: --> It's not hard until distractions and noise are introduced. This divides the attention constantly by giving emphasis <!-- EMPHASIS! --> to meaningless echoes.

<!-- Define documentation in Perl. -->In Perl, comments are comments. Documentation in Perl is <acronym title="Plain old documentation">pod</acronym> <!-- Plain old documentation -->. <-- Referring to comments as copious documentation is somewhere between misleading and inaccurate. It's only documentation for a hacker who has access to the source code. Even then it has many pitfalls besides the ones demonstrated herein. The next time you want to provide documentation, do it with pod. --> Referring to comments as copious documentation is somewhere between misleading and inaccurate. It's only documentation for a hacker who has access to the source code. Even then it has many pitfalls besides the ones demonstrated herein. The next time you want to provide documentation, do it with pod.

In reply to Re^9: RFC: Using 'threads' common aspects by Your Mother
in thread RFC: Using 'threads' common aspects by DeadPoet

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.