Hey, I like Damian, and he has some great ideas, and has produced some amazing modules and applications with Perl. But I'm not going to write my code so it looks exactly like Damian's. No offense, nothing personal, it's just that I have a style I'm comfortable and doesn't do me any grief. While his book offers some very intelligent and useful best practices, you needn't cling to them as though you'll be left behind or shunned if you don't.
Damian finds that naming his references in a self-indicative way helps him (and readers of his code, no doubt) identify them and reduce coding mistakes. Bully for him! But I don't need to. And you sound like you don't either.
I'm not trying to belittle Damian or his Best Practices book; all I'm trying to say is that there is more than one way to do it, and Damian is explaining a couple of those ways. Absorb it, adopt what you like, recognize what you don't like, and deal with 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.
|
