Perl Medic a disappointment? How so?
It doesn't quite deliver on its cover promises. Perl Medic is a good book that I would recommend to friends learning Perl, but I fail to see how it's really to do with the medic part. The part in the beginning of the book, about politics around programming in the professional world, is very valuable information one doesn't read in other places. The rest of the book appears to be written for beginning programmers, who in my opinion will benefit from a book like Beginning Perl.
I expected an advanced level book, written to help maintaining awkward legacy code. The text on the cover fortified that expectation. I also expected more examples of what one will encounter. Simple things like how for (@_) { ... } in older versions of Perl didn't check if something was read only, and that you can often fix this by simply copying the array, like so: for (my @copy = @_) { ... }. It doesn't have enough of that kind of Perl-specific advice, that is necessary to effectively deal with old and broken code you inherit.
-
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.
|