On Fri, Feb 06, 2004 at 01:46:12PM -0600, david wrote: > How about a module-authors BCP document Sure. We need a dedicated man page for module authors anyway. > and a heavy module template that includes stubs for all best current > module-authoring practices? Not in h2xs, it already does too much as it is. I'm not a fan of "throw lots of commented out code and instructions into a template" as a method of educating, as you've probably gathered. Also, wadding all best practices together is a pretty poor practice. What might be an interesting experiment is a simple web form to generate module templates. It has a bunch of checkboxes for various widgets and doodads that one might want in their module and, after the author picks what they want, it assembles it into a usable template. The advantage of a web form over a CLI like h2xs is you don't have to wade through all the obscure command line switches. All the functionality can be clearly described next to each checkbox. And you don't have to wait for the next version of Perl to use it. -- Michael G Schwern schwern@pobox.com http://www.pobox.com/~schwern/ Playstation? Of course Perl runs on Playstation. -- Jarkko Hietaniemi