Laufeyjarson writes…

The Perl Best Practices suggest to align things vertically.  They like to apace things out into neat rows of equals, fat commas, braces, and parenthesis.  Columns of data, when it will fit, are also approved of. Read the rest of this entry »

The PBP suggests that you don’t “cuddle” an else.  This means that the else and it’s opening parenthesis starts on its own line: Read the rest of this entry »

The suggestion in this one was very simple, “Code in paragraphs.”  Deceptively simple, because it means different things to different people. Read the rest of this entry »

The Best Practices tell us never to place two statements on the same line.

In general, I agree with this, and find it a workable thing to do.  There’s a few cases I forget, or decide not to.  In most of them, it comes back to bite me later, and I wish I’d listened.

At the end of the day, I like whitespace, so yes, use a new line.

The PBP suggests using spaces to indent all code lines, instead of hard tabs.  The hard tab character should appear nowhere in a file.

I disagree with this, but have given up the argument and simply do it anyway.  I feel it a minor loss, and not worth the confusion it causes from people who don’t understand hard tabs. Read the rest of this entry »

The PBP suggests using four space indentation levels.

The book goes into many reasons for this.  It suggests that I’m an “ancient coding master” because I learned with eight columns, and find that a perfectly acceptable number.  Cue; GET OFF MY LAWN!  =) Read the rest of this entry »