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 credibility sorely lacking in Perl.

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, a somewhat uncharted area. Specific questions relating to how the book fits a real software development problem would be very useful. A section meant to catalog 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.