Once you figure out the syntax, you'll be OK. There's a lot of easy-to-find reference. Make sure you test very small sections of code on their own and insert it into your programs when you get it working. Then refer to your working programs (copy & paste) when you make others.

Again, much credit needs to be given to Mr Stein, but Paul DuBois' Book MySql and Perl For The Web explains CGI.pm much better (you'll still need Stein's book if you're going to be serious about CGI) with examples that really,really, work, extreme attention to detail, and incredible organization.

Once you figure out the syntax, you'll be OK. There's a lot of easy-to-find reference. Make sure you test very small sections of code on their own and insert it into your programs when you get it working. Then refer to your working programs (copy & paste) when you make others.

Again, much credit needs to be given to Mr Stein, but Paul DuBois' Book MySql and Perl For The Web explains CGI.pm much better (you'll still need Stein's book if you're going to be serious about CGI) with examples that really,really, work, extreme attention to detail, and incredible organization.

The reader should be able to walk away from the book with the ability to create simple websites which take and respond to user input. The potential CGI.pm programmer will gain a fundamental knowledge of the module, its interface, and how it may be used to generate HTML. The text also includes a very detailed reference guide which may appeal to those people who prefer to hold what they're reading.

While the book was published back in 1998, it hasn't become outdated. It is pleasantly surprising that CGI.pm's interface has changed so little. Support for new standards like XHTML have been added since the book was originally published, but have had little net effect on the use of CGI.pm itself.

Why CGI? Isn't that the way people used to write dynamic web pages? Yes. And where portability concerns outweigh performance, it still is. Also, if you're a relative novice or don't have an endless supply of round tuits, CGI programming may present the lowest barrier of entry into dynamic web programming.

Even if you later move on to one of the newer templating systems a fundamental knowledge of CGI.pm and how it works will still be useful. Not to mention that some of the templating systems for instance HTML::Mason will run on top of CGI, even though most are primarily designed to work with Apache and mod_perl. For those who would appreciate a short description of what mod_perl is, it basically puts a copy of Perl inside the Apache executable making powerful hooks available to perl scripts and avoiding the overhead of executing a separate process for each CGI script.

The author of the book, Lincoln Stein, is also the author of the module itself. In the book, Stein takes the reader through a gradual progression of scenarios and solutions. The explanations are thorough and the pace gradually takes the reader into more advanced topics. In short, it is a concise introduction to CGI programming with Perl.

Low level details, like how CGI works under the hood and more advanced topics like security, cascading style sheets, javascript, and persistence are touched upon but not covered in particular depth. The author does however provide many timely references to books and websites where the reader can find more information on those topics.

A basic knowledge of Perl is helpful in getting the most out of this book. I would strongly recommend reading at least the first few chapters of "Learning Perl" for people without any other programming skills, or the first few chapters of "Programming Perl" for those coming to Perl from another language.

I found that using this book in conjunction with "MySQL and Perl for the Web" gave me a great experience. Even though the latter book sounds like it is aimed more at the DB end, it has a couple good chapters on getting up and running with Perl/CGI and mod_perl. Was also quite thankful that Lincoln covered both the traditional and Object-Oriented interfaces to the module. Great Book!

The reader should be able to walk away from the book with the ability to create simple websites which take and respond to user input. The potential CGI.pm programmer will gain a fundamental knowledge of the module, its interface, and how it may be used to generate HTML. The text also includes a very detailed reference guide which may appeal to those people who prefer to hold what they're reading.

While the book was published back in 1998, it hasn't become outdated. It is pleasantly surprising that CGI.pm's interface has changed so little. Support for new standards like XHTML have been added since the book was originally published, but have had little net effect on the use of CGI.pm itself.

Why CGI? Isn't that the way people used to write dynamic web pages? Yes. And where portability concerns outweigh performance, it still is. Also, if you're a relative novice or don't have an endless supply of round tuits, CGI programming may present the lowest barrier of entry into dynamic web programming.

Even if you later move on to one of the newer templating systems a fundamental knowledge of CGI.pm and how it works will still be useful. Not to mention that some of the templating systems for instance HTML::Mason will run on top of CGI, even though most are primarily designed to work with Apache and mod_perl. For those who would appreciate a short description of what mod_perl is, it basically puts a copy of Perl inside the Apache executable making powerful hooks available to perl scripts and avoiding the overhead of executing a separate process for each CGI script.

The author of the book, Lincoln Stein, is also the author of the module itself. In the book, Stein takes the reader through a gradual progression of scenarios and solutions. The explanations are thorough and the pace gradually takes the reader into more advanced topics. In short, it is a concise introduction to CGI programming with Perl.

Low level details, like how CGI works under the hood and more advanced topics like security, cascading style sheets, javascript, and persistence are touched upon but not covered in particular depth. The author does however provide many timely references to books and websites where the reader can find more information on those topics.

Now I have to ask: how on earth can a book be designed as poorly as that? Whoever the designer is, I'd strongly recommed him(her?) to buy "The Form of the Book" by Jan Tchicold (hope I spelled it correctly).

The book is easy to follow and contains some illustrative examples that are also available on a companion website. My one and only complaint is the price of the book: it seems a little steep given that most of the material in there is available on the web in one form or another for free. If you don't want to take the time printing and compiling, then this is an excellent manual that will soon sport bookmarks and highlights throughout.