Language:
English
Pages:
xxii, 517
,
ill. ;
,
24 cm
Edition:
1st ed.
Keywords:
Perl (Computer program language)
;
Electronic books ; local
Abstract:
Many programmers code by instinct, relying on convenient habits ora "style" they picked up early on. They aren't conscious of all thechoices they make, like how they format their source, the namesthey use for variables, or the kinds of loops they use. They'refocused entirely on problems they're solving, solutions they'recreating, and algorithms they're implementing. So they write codein the way that seems natural, that happens intuitively, and thatfeels good. But if you're serious about your profession, intuition isn'tenough. Perl Best Practices author Damian Conway explainsthat rules, conventions, standards, and practices not only helpprogrammers communicate and coordinate with one another, they alsoprovide a reliable framework for thinking about problems, and acommon language for expressing solutions. This is especiallycritical in Perl, because the language is designed to offer manyways to accomplish the same task, and consequently it supports manyincompatible dialects. With a good dose of Aussie humor, Dr. Conway (familiar to manyin the Perl community) offers 256 guidelines on the art of codingto help you write better Perl code--in fact, the best Perl code youpossibly can. The guidelines cover code layout, naming conventions,choice of data and control structures, program decomposition,interface design and implementation, modularity, objectorientation, error handling, testing, and debugging. They're designed to work together to produce code that is clear,robust, efficient, maintainable, and concise, but Dr. Conwaydoesn't pretend that this is the one true universal and unequivocalset of best practices. Instead, Perl Best Practices offerscoherent and widely applicable suggestions based on real-worldexperience of how code is actually written, rather than onsomeone's ivory-tower theories on how software ought to becreated. Most of all, Perl Best Practices offers guidelines thatactually work, and that many developers around the world arealready using. Much like Perl itself, these guidelines are abouthelping you to get your job done, without getting in the way. Praise for Perl Best Practices from Perl communitymembers: "As a manager of a large Perl project, I'd ensure that everymember of my team has a copy of Perl Best Practices on theirdesk, and use it as the basis for an in-house style guide." --Randal Schwartz "There are no more excuses for writing bad Perl programs. Alllevels of Perl programmer will be more productive after readingthis book." ...
Note:
Includes bibliographical references (p. 493-494) and index
URL:
https://learning.oreilly.com/library/view/-/0596001738/?ar
Permalink
