I voted for Programming Perl (I've got the 2d edition), despite its information being largely replicated in the man pages. Since I program mostly for Windows, I needed to install Perl before I had access to the man pages; Programming Perl gave me enough useful information to convince me to do that and enough information to get started. I also currently own Learning Perl, which I found to be too basic, Mastering Perl/Tk, which is specialized (and, in my opinion, it could be better organized), and Perl Cookbook, which is handy when I want to steal some codeget inspired to find a solution to a specific problem. I still find the camel book to be useful, in that it's frequently easier for me to use a book than online man pages (especially with my randomly-prone-to-demonstrate-why-I-hate-Windows workplace desktop).
emc
"Being forced to write comments actually improves code, because it is easier to fix a crock than to explain it. " —G. Steele
-
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.
|
