* Barrie Slaymaker <[EMAIL PROTECTED]> [2002-12-20 04:05]:
> Part of QA is defining best practices. I've been encoding a few
> operations I use a lot when writing new perl module distributions in
> to script form to make my code and POD more consistent.
This is great. I keep meaning to do something like this myself, get
about halfway there, and then end up doing something else. Good work.
- Using Template.{t,pm} is a little counter-intuitive -- this looks
like it's a ragular Perl module, instead of a template (despite the
name). I'd use something like _skeleton.pm and _skeleton.t for
these files.
- Something that I would consider adding is the ability to choose
different Template.pm's -- for example, if you are creating an Apache
module, as opposed to a POE component, the template you will want to
use will be radically different. I think something like named templates
would work, so that:
newpmdist -t Apache Foo::Bar
Would look for Apache.pm in ~/.newpm instead of Template.pm. Of course,
this will break if you're writing a Template Toolkit plugin, but see my
previous comment about _skeleton.pm.
Overall, it looks very good. When's the release party? :)
(darren)
--
Don't be ashamed to say what you are not ashamed to think.
