LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Reviews > Books > Programming
User Name
Password

Notices

Search · Register · Submit New Review · Download your favorite Linux Distributions ·
 

Perl Medic: Transforming Legacy Code
Reviews Views Date of last review
1 20841 03-27-2004
spacer
Recommended By Average Price Average Rating
100% of reviewers $34.99 8.0
spacer


Description: Today's Perl developers spend 60-80% of their time working with existing Perl code. Now, there's a start-to-finish guide to understanding that code, maintaining it, updating it, and refactoring it for maximum performance and reliability. Peter J. Scott, lead author of Perl Debugged, has written the first systematic guide to Perl software engineering. Through extensive examples, he shows how to bring powerful discipline, consistency, and structure to any Perl program-new or old. If you've ever inherited Perl code that's hard to maintain, if you write Perl code others will read, if you want to write code that'll be easier for you to maintain, the book that comes to your rescue is Perl Medic.
Keywords: Peter Scott Perl
Publisher: Addison-Wesley
ISBN: 0201795264


Author
Post A Reply 
Old 03-27-2004, 11:37 AM   #1
XavierP
 
Registered: Nov 2002
Distribution: Lubuntu
Posts: 19,174

Rep: Reputation:
Would you recommend the product? yes | Price you paid?: $34.99 | Rating: 8

Pros: Great resource for Perl programmers who may have to amend or update someone else's code
Cons: Not much use to anyone else



The excellent Groklaw has the following disclaimer: IANAL (I Am Not A Lawyer), so I'd like to add the following to this review IANAPP (I Am Not A Perl Programmer). With that in mind, on to the review.

This book is aimed at people who have to maintain, fix or update Perl code written by someone else. Since I do not fall into that category (see above), I cannot vouch for the methods iven. I can, however, discuss the content and format. This book is 301 pages long and covers (AFAIK) the aspects of what to look for and how to do it. Interestingly for a programmers guide, it also delves into the 'human aspect' - how to approach the original coder, not badmouthing the team who worked on it and things like that. I didn't expect to see that and it is welcome.

It has 12 chapters and an appendix of source code. Without listing them, the chapters are about the how and the why of taking on the code - from being forced to do it as your job to doing it to make it better and more recent.

This book has many examples of code and of tests and modules. It contains good advice to the maintainer and has a large number of web links and references.

The book is well written, funny in places and has some great quotes to head up the chapters. While I couldn't really make use of this book right now (but one day.....) I would definitely recommend it to the target audience.
 




  



All times are GMT -5. The time now is 11:56 PM.

Main Menu
Advertisement

My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration