I couldn't agree more. Sadly, I did the same thing as Ovid, since I was handed a website and told to fix it up in 3 days. I picked up Castro's book since it was the thinnest one on the shelf containing both "CGI" and "Perl" in the title. The first drafts of all my scripts used her hacked-together CGI routines... badly. Some months later (after having read the ORA books on Perl and CGI), I went back to those scripts and laughed myself silly. I rewrote the site using DBI and CGI.pm in a fraction of the time and space it had originally taken me. I don't think that introducing Perl and CGI concurrently is necessarily a bad idea, but doing it in a book that's only 272 pages cover to cover is insane. Newbies beware: this book is full of bad habits and lacks critical information. Experienced PHs won't have any use for it at all. I'll echo Ovid's summary: don't bother.
-
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.
|
