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.
  • What entry was the whitespace problem one? That sounds like an interesting slant that I haven't heard before.

    • It was incidental to a discussion about symbol chunking in Perl 6:

      I have trouble reading code without judicious vertical whitespace to separate paragraphs, so Python can be a chore. (Is this empty line the end of an block or just a paragraph within the block?)

      See Re:DL$MT%DF@#(hhh [perl.org].

      • Hmmm, maybe I read your post first, but I've noticed that too. The little Python I've seen tend to have rather few blank lines to separate paragraphs of code. No rhythm. No flow.

        Another counter to the "oooh, it's naturally easy to maintain".

        Elisp code seem to be similar in regard to compactness, but probably for different reasons. Maybe I still haven't got the proper Lisp eye, but I find that slightly annoying.

        • The little Python I've seen tend to have rather few blank lines to separate paragraphs of code.

          That's exactly it.

          Consider also that the human brain can count by view somewhere between five to seven items. You have to count by counting, if there are any more items. Compare indentation levels of two pieces of code separated by other lines of code or blank lines, especially if there are multiple indentation levels. It's not as easy as it might seem.

          People will argue that you should write clear, concise co