I would hate for the book to fall into the hands of manager who does not know perl and blindly dictates that the whole book will become the company coding standard.
Never had a manager who thought there was a benefit of enforcing coding styles, but I've met many coworkers who started suggesting coding styles. Most of them, they say "perhaps we should start with PBP". Those people can be easily countered: if you have converted all your OO classes to use Class::Std, come back and we'll continue the discussion". I'm still waiting for the first person to do so.
PBP has some interesting arguments. But nowadays, I only use my copy of PBP to whack people who defend their style with "but PBP says so" over their head. My copy is quite tattered and bloody, as I'm not afraid to use it.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|