I agree with sschneid -- in fact, I often have a hard time reading code that isn't colored. I've gotten quite used to comments being colored green, so I either look to green text first or last (depending on the situation).

And even colorblind people can distinguish between shades, so gray text doesn't stand out as much as black text. So by making comments and such lighter, it's easier to ignore when appropriate. You've also added some bold to the code snippet above, and that's not dependent on color.

IMHO, teaching students to read colored code would be about 1000 times easier than teaching them to read mono-color code.

In reply to Re: Documenting code by Nkuvu
in thread Documenting code by traveler

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.