Laufeyjarson writes…

In those places you do actually need both the key and value, you will have to go ahead and do the lookup on the key to get the value.  The PBP reminds us to only do that once, instead of many times in the loop. (more…)

The Best Practice suggests avoiding subscripting arrays or hashes within loops.  They have a good reason too! (more…)

The Best Practices cast the use of C Style For Loops out of our lexicon.  Personally, I don’t get why this is, but haven’t needed them in a while. (more…)

The PBP simply states, “Don’t use unless or until at all.”  I don’t agree with the strength of that statement. (more…)

The PBP suggests one simple thing for using other postfix control structures, such as unless, for, while, and until.  It says: Don’t. (more…)

Having given a concrete statement of “… always use the block form of if.” the PBP then gives you a time and place to use a postix if.  It says that’s okay if  you’re it for using a flow control statement like next, return, last, etc. (more…)

The first entry in the “Control Structures” group regards the humble if statement.  Perl being perl, the if statement is more complex than it looks, and the Best Practices casually state, “… always use the block form of if.” (more…)

The Best Practices suggest extracting key or index lists out of large slices and using hashes to manage them. (more…)

Our favorite reference suggests that working with slices is easier when those items are aligned in columns.  Sometimes. (more…)

Everyone’s favorite set of Perl guideliens tells is not to forget about the awesome power of array slices!  That’s smart, too. (more…)