> Fortunately, this is a fairly rote process. Unfortunately, its not
> easily automatable since the current test naming scheme is
> inconsistant. Also, some tests rely on their name being what it is.
> No worries, though, this can be done as an incremental process.
>
> Thought... we might want to add a "so, you're not a C programmer?"
> section to perlhack mentioning jobs like this for those who want to
> get involved but not yet ready to hack core.
>
> Anyone see anything horribly wrong with this?
Looks good to me.
One additional point to consider and solve is the BEGIN 'preamble' we
now add to each test to make certain we are in a known directory, and
more importantly, that we are running the tests using *the* lib/ of
the Perl we are building and not some other lib. Having to add that
preamble manually to the lib tests is clunky, but if I pull a new
module release out of CPAN, the preamble is not there, so...
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
