The PBP suggests using a 78-column line length.
I’m good with this. I don’t feel the need to be a pedant about it, but I like the idea in general. Read the rest of this entry »
PBP: 009 Line Lengths
May 29th, 2014PBP: 008 Commas
May 26th, 2014The suggestion is to put a comma after every value in a list, even the last which doesn’t need it. Read the rest of this entry »
PBP: 007 Semicolons
May 22nd, 2014The suggestion here is to place a semicolon after every statement. I agree with this, even if it isn’t technically needed. The only place I’ll skip it is if it is a function returning a constant value, and that’s all that is in the function, like this: Read the rest of this entry »
YAPC::NA or not?
May 19th, 2014I keep thinking I should go to YAPC::NA. I’ve had co-workers suggest it. I can get myself there, I can get the time off work. All the blogs I’ve read say it’ll be great!
I don’t see the greatness on the web anywhere, though. Read the rest of this entry »
PBP: 006 Operators
May 19th, 2014PBP says to put whitespace around binary operators. This, I entirely agree with. It also notes to keep unary operators together with their operand. This, too, I think is a good idea. Read the rest of this entry »
PBP: 005 Keys and Indices
May 15th, 2014The PBP suggests putting whitespace between keys or indices and their brackets.
I find this a good suggestion, although I forget to do it sometimes. I do it for all complex statements, but forget for simple cases.
This is a place perltidy is a big help.
PBP: 004 Builtins
May 12th, 2014The suggestion in this section is not to use parenthesis for builtins and builtin-like functions.
I’m not sure why differentiating between builtins and functions is particularly useful, but I don’t object to the idea and found it easy to get used to.
