[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-hackers] submission of Perl Design Patterns Book -

From: scott
Subject: [Savannah-hackers] submission of Perl Design Patterns Book -
Date: Wed, 25 Sep 2002 20:25:32 -0400
User-agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.1) Gecko/20020826

A package was submitted to
This mail was sent to address@hidden, address@hidden

Scott Walters <address@hidden> described the package as follows:
License: fdl
Other License: 
Package: Perl Design Patterns Book
System name: perlpatbook
Type: non-GNU

Perl Design Patterns documents Perl style and design/analysis. Design Patterns 
are a hands-on, pragmatic object oriented approach, in contrast to the vague, 
theory ridden texts IT is plagued with. We
cover dynamic programming, lambda abstraction, and other techniques with the 
same approach.

Moderate through advanced experience level. Similar to \"Design Pattern\" books 
for Java, C++, influenced heavily by \"A Pattern Language\", Christopher 

At the time of this writing, approximately 100
pages worth of content exist, entirely covering the traditional,
expected patterns. A snapshot can be fetched from
Browsing the Wiki directly at 
directly has the advantage of allowing you submit questions, corrections, 
ideas, and amendments directly, as well as browse non-linearly. CVS access is
available as well, in some cases.

Ultimate goal is to produce a bound, printed manual, preserving the
GNU FDL license. The text should be useful as a college textbook
on object oriented methods, an advanced language textbook using Perl,
a guide for \"Enterprise\" software architecture using Perl, as well as merely 
a Perl-centric crash course on design patterns. Java and Smalltalk have long 
embraced design patterns, creating a commercial crediability sorely lacking in 

What is lacking? Proofreaders: My spelling is atrocious, but I can
fix spelling and typographical errors in due time. Feedback on readability, 
accuracy, and comprehensiveness is much more important. Many sections are 
missing entirely or only very sketchy; others have not yet been discovered yet. 
Having addressed boring OO stuff, I\'m expanding into the realm of dynamic 
languages, which is hithero uncharted. Specific questions relating to how the 
book fits a real
software development problem would be very useful. A section meant to catalogue 
Perl modules related to software development, interoperability and frameworks 
has barely been started. Most of all, please read as much as you can stand, and 
tell me why you do or don\'t like it.

Other Software Required:
Perl 5.6.0 or later.

Other Comments:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]