I think it's a lucky coincidence that the console width is near the optimal width for eye movement.

I think it's an excellent design choice that the console width is near the optimal width for eye movement.

While it's not a cast-iron rule, I do tend to keep code lines under 80 chars. It's easier to read, easier to debug, prints neatly on pretty much any output device and encourages critical thinking. All IMHO. For collaborative code, perltidy is the winner.

perlcritic (at least version 1.125) seems perfectly happy with absurdly long lines, which is somewhat surprising.

In reply to Re^2: To <=80 char code line length or not by hippo
in thread To <=80 char code line length or not by stevieb

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.