Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I like most of your outline, especially the performance chapter, but the chapter about TIE, AUTOLOAD, source filters, symbol tables, and type globs looks like the script of a horror movie to me. These are things that I expect mature coders to understand and almost totally avoid. I suppose they have to learn them somewhere though. I do like the part about error handling. Many perl coders I meet don't have much knowledge about this.

    If I were going to look for a training manual for people I would like

    • I'm not sure what constitutes mastery, and it's something that I have to define. However, getting through the book won't make anyone a Perl master. I want to teach how to master Perl, meaning that once they've gone through the book they should be able to answer their own questions. That's a hard thing to show in the outline because it comes in bits and pieces in all of the other topics.

      I also avoid subjects covered much better in other books (so maybe I should have a chapter on other books). Perl Best Practices, Advanced Perl Programming, Programming the Perl DBI, and Perl Testing: A Developer's Notebook cover those things in much much depth.

      The new editions of Learning Perl and Intermediate Perl cover CPAN. I insisted on it because the change in beginner Perl has shifted in that direction. Almost every beginner I teach immediately has a module in mind for a script they need to write. Indeed, CPAN might be driving people to Perl (even if relunctantly).

      The proposal is very far from finished, so your comments are really helpful. Thanks :)