[RFC] Module::Husbandry

2002-12-20 Thread Barrie Slaymaker
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. Here's a prerelease of them: http://users.telerama.com/~rbs/src/Module-Husbandry-0.0001.tar.gz and the

Re: [RFC] Module::Husbandry

2002-12-20 Thread darren chamberlain
* 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 someth

Re: [RFC] Module::Husbandry

2002-12-20 Thread Nicholas Clark
On Fri, Dec 20, 2002 at 08:17:16AM -0500, darren chamberlain wrote: > 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 i

Re: [RFC] Module::Husbandry

2002-12-20 Thread darren chamberlain
* Nicholas Clark <[EMAIL PROTECTED]> [2002-12-20 08:30]: > Aargh. A bad pun has landed in my head and demands that I share it: > > tePMlate.pm And templaTe.t for the test skeleton. I like it. (darren) -- The higher we soar the smaller we appear to those who cannot fly. -- Friedrich Niet

Re: [RFC] Module::Husbandry

2002-12-20 Thread Barrie Slaymaker
On Fri, Dec 20, 2002 at 08:17:16AM -0500, darren chamberlain wrote: > * 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 m

Re: [RFC] Module::Husbandry

2002-12-20 Thread darren chamberlain
* Barrie Slaymaker <[EMAIL PROTECTED]> [2002-12-20 08:52]: > I've kludged code to peer in to TT2 templates to get at [%META%] > declarations (it does not allow this by default AFAICS, surprisingly, > I had to grovel through the template object's guts for meta info), and > this has proven to be a us

Re: [RFC] Module::Husbandry

2002-12-20 Thread Barrie Slaymaker
On Fri, Dec 20, 2002 at 09:12:09AM -0500, darren chamberlain wrote: > * Barrie Slaymaker <[EMAIL PROTECTED]> [2002-12-20 08:52]: > > I've kludged code to peer in to TT2 templates to get at [%META%] > > declarations (it does not allow this by default AFAICS, surprisingly, > > I had to grovel through

Re: [RFC] Module::Husbandry

2002-12-20 Thread darren chamberlain
* Barrie Slaymaker <[EMAIL PROTECTED]> [2002-12-20 09:20]: > On Fri, Dec 20, 2002 at 09:12:09AM -0500, darren chamberlain wrote: > > Oh, that's a pretty straightforward (though completely undocumented) > > one: > > heh, it's not straightforward if it's undocumented. Yessirree, that's > my motto.

[OT] TT2 docs

2002-12-20 Thread Barrie Slaymaker
On Fri, Dec 20, 2002 at 09:54:50AM -0500, darren chamberlain wrote: > > The docs for Template::Provider state: > > fetch($name) fetch()ing's the easy part. Even *I* got that far long ago. It's the fact that you can coax metadata out of the template objects with AUTOLOADed methods that I didn

Re: [OT] TT2 docs

2002-12-20 Thread darren chamberlain
* Barrie Slaymaker <[EMAIL PROTECTED]> [2002-12-20 10:08]: > On Fri, Dec 20, 2002 at 09:54:50AM -0500, darren chamberlain wrote: > > > > The docs for Template::Provider state: > > > > fetch($name) > > fetch()ing's the easy part. Even *I* got that far long ago. Ah, sorry. > It's the fact tha