Laufeyjarson writes…

The PBP simply states, “Don’t use unless or until at all.”  I don’t agree with the strength of that statement. Read the rest of this entry »

The PBP suggests one simple thing for using other postfix control structures, such as unless, for, while, and until.  It says: Don’t. Read the rest of this entry »

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. Read the rest of this entry »

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.” Read the rest of this entry »

The Best Practices suggest extracting key or index lists out of large slices and using hashes to manage them. Read the rest of this entry »

Our favorite reference suggests that working with slices is easier when those items are aligned in columns.  Sometimes. Read the rest of this entry »

Everyone’s favorite set of Perl guideliens tells is not to forget about the awesome power of array slices!  That’s smart, too. Read the rest of this entry »

The PBP reminds us that we can use negative indexes to access arrays in reverse, instead of having to do calculations for it.  It suggests several useful reasons, including readability and getting the interpreter to complain in some cases instead of silently doing the wrong thing.  I don’t feel that strongly about this suggestion, but do follow it. Read the rest of this entry »

Mr. Conway suggests that you be wary of any modification to $_.  Personally, I take it further than that, and try never to use the thing at all. Read the rest of this entry »

Lots of people (not just the Best Practices) tell you never to use the regex match variables.  Listen to them! Read the rest of this entry »