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.)
I insinuated in the RFC that Pod::Tests is to simply go through the
POD and pull out the "=for testing" and "=also for example" blocks and
present them to the module user in some data structure. Then whatever
program using Pod::Tests can determine what to actually do with them.
pod2tests would actually contain the logic for producing the .t files.
Looking at the code, I *think* that's the way you made it work... I
guess.
I'm confused. But somebody's written code! Hurray!
PS I really don't like "=also_for". Not only does it look bad, but also
means we need "=also_begin" and "=also_end" as individual tags.
PPS We need a CVS repository. Ask is mum on the subject. Should be
just punt and use sourceforge?
> sub parse_from_file {
> my $self = shift;
> my ( $file_name, $dest_dir ) = @_ ;
> $self->{DEST_DIR} = $dest_dir ;
> croak "No destination directory supplied"
> unless defined $dest_dir && length $dest_dir ;
> $self->parse_from_file( $file_name ) ;
> }
Shouldn't that be $self->SUPER::parse_from_file( $file_name )?
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee Ashuranse
I'm successful because I'm lucky. The harder I work, the luckier I get.
