The Best Practices suggest avoiding string eval. Read the rest of this entry »
PBP: 105 Avoid string eval
June 29th, 2015PBP: 104 Variable-Width Data
June 25th, 2015The Best Practices suggest using CPAN modules for more complex data parsing, instead of trying to roll your own. Read the rest of this entry »
PBP: 103 Separated Data
June 22nd, 2015The Book suggests using split to take apart separated data with simple separators. Read the rest of this entry »
PBP 102: Fixed-width Data
June 18th, 2015The PBP suggests we use unpack to take apart fixed-width data. Read the rest of this entry »
PBP: 101 Reversing Scalars
June 15th, 2015The PBP suggests that when you want to reverse a scalar, you explicitly state this with ‘scalar reverse $variable’ instead of just using reverse on it. It suggests this both makes explicit, and regularizes the use, regardless of the context it is called in.
I don’t like this suggestion and don’t feel it is needed, but I won’t object to it because of the clear example in the book that makes it clear how it helps. I find the demand you add a ‘scalar’ all the time because sometimes it’s unclear to be a problem. I’ll probably turn off the critic warning for this, but I won’t say it’s too horrible.
PBP: 100 Reversing Lists
June 11th, 2015Mr. Conway suggets using the reverse builtin when appropriate. This includes with sort, and for counting backwards. Read the rest of this entry »
PBP: 099 Sorting
June 8th, 2015The Best Practices have things to say about many of Perl’s built-in functions. Besides the general advice “use them” – which I agree with – it has some specific suggestions. First up: Sorting Read the rest of this entry »
At YAPC::NA
June 7th, 2015Not only did I make all the arrangements in time, I made my flight and have found the hotel. I am checked in and sitting in a room full of geeks having a hackathon.
It’s a room full of pretty serious computer users. I am not the only one in the room who has configured UUCP, for example.
Fun so far!
PBP: 098 Proofreading
June 1st, 2015It is a Best Practice to check the spelling, syntax, and sanity of your documentation. I agree with this, strongly. Read the rest of this entry »
PBP: 097 Discursive Documentation
May 7th, 2015The PBP suggests a way to put longer blocks of documentation in code, by using the =for or =begin/=end notation in POD. By labeling these with a “formatter” that does not exist, they’ll never be output and are merely ignored by the compiler and for the author’s use. Read the rest of this entry »