Michael G Schwern wrote:
>
> On Fri, Sep 01, 2000 at 12:18:32AM -0400, Barrie Slaymaker wrote:
> > Here's a quick take on a Pod::Tests, I threw it together as part of my =also
> > prototype code.
>
> Looking at the docs... umm, how do you use it? Let's assume I don't
> know how to use Pod::Select (which isn't too far from the truth.)
Forgot to address this in the last message. The docs gave how to use it
in the SYNOPSIS, a quick example of the POD commands it understands, and an
explicit statement that it uses no functionality specific to Pod::Select and
that in a 'real' implementation it would just inherit from Pod::Parser. So,
that should have addressed 75% of your question, modulo my usual clear-as-mud
technical writing. Sorry if it was too opaque.
What it didn't say is that it creates test files in the destination directory
you pass to the parse methods, and puts all the test code found in the source
file in to the appropriate destination files. I've revamped it, and written
a Pod::StdParser, announcement to follow later tonight.
And the code was a little overly familiar with Pod::Parser's internals because
of the way I hacked things to prove the concept to myself.
> PPS We need a CVS repository. Ask is mum on the subject. Should be
> just punt and use sourceforge?
Cool (esp. given Ask's recent reply): go create a project perl-qa!
- Barrie
