Laufeyjarson writes…

The PBP tells us to use here documents when a multi line string is too long.  It suggests two lines is long enough for a single string, and anything longer should be a here document. (more…)

The PBP suggests breaking your strings on any embedded newlines so they look in code something like they’ll look when output. (more…)

Great big numbers full of digits are hard to read and be sure they’re right, so the PBP suggest using the magic underscore in the numbers to spread them out and make them more readable. (more…)

Best Practice: Don’t pad decimal numbers with leading zeroes. (more…)

The PBP suggests using named escape characters instead of hardcoding ASCII values.  It has some reasonable examples, such as this: (more…)

Much like empty strings, the PBP suggests being careful of how you write single character strings.  It points out a number of them it considers “ambiguous”, including: (more…)

Mr. Conway’s book suggests that constants are good but “use constant;” is the wrong way to go about them.  It suggests the Readonly module.  Later commenters have suggested Const::Fast instead.  Feh, I say. (more…)

The PBP suggests never using “” or ” for empty strings, and using q{} instead.  Because clearly that’s so much more readable. (more…)

The PBP suggests using interpolating string delimiters only when they’re needed.  How much of my time do I get to waste changing single to double quotes because there’s a contraction in a message, or the other way because there isn’t? (more…)

Here’s where the PBP tells you to prefix “internal use only” subroutines with an underscore.  Why it calls them “utility subroutines” I don’t know. (more…)