As you and others have (and will) point out, much of what is in PBP is confirmation of our ideals. That doesn't mean we always follow them.
As for what I started doing as a result of reading:
- I'm much more careful to use single quotes when not interpolating.
- I created a button in vi to type use Data::Dumper; warn Dumper( );
- I use warn for all debugging.
- File handles are now lexical scalars.
There are probably others, but those are the ones that spring fastest to mind.
There are some that didn't take with me. I refuse to give up unless. And I don't much like cascading ternaries, since so many people are not used to reading them. I'm not paranoid enough for inside out objects (and they make dumping the object harder).
None of this is criticism for the book. Damian says it should start a dicussion and lead to careful thought about practices. It did that for me.
Since you brought it up, I should probably give it another quick read to see if I'm living up to my ideals.
Phil
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.