Re: 20 most important Perl Best Practices

[pvaldes]

This is a false problem. Some of this advices are only cosmetic. People are different and always will be, you can't expect that the next guy that will read your code have the same brain structure or habits that you

I tend to think in terms of structures, so I personally hate the "stammer code" extending over seven pages

while (blah)
{... cri cri
if (/this/)
{... cri cri
do thiiiis
}.... cri cri

elseee ....
  {.... cri cri
do thaaaat
 }
}... violins

An excess of hesitation really makes me feel very nervous. As long as all options fit in a line, this is much better for me

While(blah){
 if(/match/){  do_this()   } 
 else       {  do_that()   } 
 # no, I don't like the "} else" way, you lose the symmetry
}
(blank line here)

If you have a legacy code that you need to maintain, and you like, i.e, to see a carriage return between "if(blah)" and "{" don't suffer seing this disgusting (for you) structure all the time... make a copy of the code, lock the original in a safe place under seven keys and USE PERL regexes to "reorder the furniture of this room" in the copy as you like. What is the big fuss?

s/"I really hate this stupid way of writing code in a single line"/"That's \n much \n better now"/

If you add a sentence to a block and forget the ";" the program will emit a warning with the number of the exact offending line. Solution: read the warnings...

I you can use five characters to build your functional code structure don't use six (unless the omited character makes the code unreadable), but if you can use six characters to document your code don't use five.