Perl Core Language

Perl Core Language, Second Edition takes you from the basic language up through object Perl, Modules, CGI, XML, and Perl Debugging.


February 01, 2005
URL:http://www.drdobbs.com/web-development/perl-core-language/184416193

Jack J. Woehr is an independent consultant and team mentor practicing in Colorado. He can be contacted at http://www.softwoehr.com/.


Perl Core Language, Second Edition
Steven Holzner
Paraglyph Press, 2004
528 pp., $29.99
ISBN 1932111921

Perl Core Language is part of Paraglyph's "Little Black Book" series, billed as "concise problem solvers." The content of Perl Core Language consists primarily of chapters in two parts. The first part of each chapter is the In Brief section (it might simply have been called "Brief"), a summary of the theme that unifies the chapter. This is followed by Immediate Solutions, topics (often occupying less than a full page), such as "Removing Trailing and Leading Spaces," "Using Array References as Hash References," or covering one of the scores of Perl function calls described by the book.

The book takes you from the basic language up through object Perl, Modules, CGI, XML, and Perl Debugging. The industry ritual of two "on beyond zebra" chapters at the end goes unchallenged: Here the extras are Chapter 20 on counters, guestbooks, e-mailers, and secure scripts; and Chapter 21 on multiuser chat, cookies, and games.

Though it starts with a Chapter on "Essential Perl" covering the boilerplate topics of downloading and installing Perl, making sure the shell interpreter can execute your scripts on any conceivable platform, language basics, and so on, Perl Core Language is not a book for learning Perl (nor for learning XML—you should be well grounded before you tackle Chapter 19, "Perl and XML"). It's a book for those who have learned Perl, and probably umpteen other languages, which explains why they need such a book open on their desk as they dive into a Perl project or merely into a day's coding. The book is the digested manual, often paired with clarifying examples composed by a skilled exigete for application on the fly. Hundreds of useful (albeit shallow) headings fit into a book under the application of such a formula, but the concision comes at a price. Holzner gets into the rhythm of his formula to the extent that, occasionally, he appears not to have parsed what he was writing for sense, as in the sprintf article:

%e - A floating-point number, in scientific notation
%E - Like %e, but using an uppercase E.
%f - A floating-point number, in fixed decimal notation.
%g - A floating-point number, in %e or %f notation
%G - Like %g, but with an uppercase G

In case you missed the error, read the %G line again. %G most definitely does not produce an "uppercase G" in its output.

Perl Core Language is another one of these books whose blurbs reference Perl 6.0 ("[C]overs the current version...as well as highlighting critical features of the upcoming 6.0 version"). Anyone following the developers' list for Perl 6 ([email protected] or in entertaining the weekly summary athttp://www.perl.com/pub/ a/2005/01/p6pdigest/20050118.html) knows that if you want to know about Perl 6, you start at http://dev.perl.org/perl6/. If you don't understand what you read there, you don't really want to know right now, anyway. In any case, for the target reader of Perl Core Language, the contours of Perl 6 can be most usefully summed up by the Magic 8-Ball: "Ask again later."

Certain other literary aspects of the work rub this reviewer the wrong way. First of all, prolific author Steven Holzner is an old hand at tech writing. Amazon offers 96 (!) of his books. Yet, oddly enough, none of these previous authorships are listed in this book under the "About the Author" heading. Second, we're sure Holzner wouldn't program a new object class merely to encapsulate one-to-one the capabilities of an extant class. Then why are the "Acknowledgments" solely aimed at the book's production team? Shouldn't the roles played by these individuals simply appear de rigeur inserted into the book by the publisher as "Credits" without reference to the author's wishes? Normative these days in tech book "Acknowledgments" are frank comments like, "I could never have done it without my wife Hroswitha, who entered therapy so she could handle my locking myself in my basement office for two years to write this book for a $7000 advance against nonexistent royalties." Now, if Holzner had offered praise to these individuals for doing their jobs skillfully despite their being woefully underpaid and abused by seven layers of lackluster management or something of the sort, there would be the kind of value added above and beyond simple credits that would justify calling it an "Acknowledgment."

The web site http://www.paraglyphpress.com/ turns out to be a tumble-down shed since the new barn got raised: http:// paraglyph.oreilly.com/. There, you'll find the link to Perl Core Language pointing to http://www.oreilly.com/catalog/1932111921/. Hardly an intuitive URL, but consolidation marches onward in tech book publishing as in all other industries. Anyway, once arrived at the cited URL, you will find none of the usual amenities: no table of contents, no sample chapter, no downloadable example code. Everything about this effort bespeaks itself of hurry, which is hardly unusual hereabouts, but rush reaches an apogee in the present case wherein the same author publishes several other books in the course of the same 12 months. Steven Holzner clearly understands Perl, has impressive authorship credits, and is approaching rough parity with Herbert Schildt, another workhorse of this industry. If only Holzner, at the peak of his form, had time to stop and smell the roses!

TPJ

Terms of Service | Privacy Statement | Copyright © 2024 UBM Tech, All rights reserved.