A. Pagaltzis wrote:
* Robert Rothenberg <[EMAIL PROTECTED]> [2005-08-21 13:40]:
No matter what wiz-bang new module starter system somebody
comes up with, there will be some kind of boilerplate text.
Unless maybe it asks you to write the documentation before you
write the module.
Maybe the solution is to a) explicitly use placeholder marks and
b) write the module starter tool in such a way that one can fill
in placeholders after initially creating the module.
That way the distro builder can find the placeholders without
groping for known boilerplate, and the user can either remove the
placeholders manually when editing, call the starter tool again
later as guidance, or just use the its postponed fill-in as part
of his personal modus operandi.
Or have Module::Starter know how to include site-local boilerplate. I
like addnig a fixed blurb on how to report bugs (and no doubt other
stuff but that's what I can think of without looking). If M::S knew how
to fetch that during a run it would save me from having to set up a
local template such as brian d foy outlined earlier.
David
