There are a fair number of documentation files in parrot that are pod
files. Most of the README files aren't pod files, but the pge README
and the tcl README are. There are several other files where the same
occurs. If there aren't any objections, I can take care of this later
on. Running(under tcsh):
find -E . -not \( -name .svn -prune \) -type f -not -perm +111 -not
-regex '.*\.([a-z0-9_]+|C)' -not -name Makefile -not -name harness
-exec podchecker '{}' \; |& grep -v 'does not contain any pod commands'
seems to find them all(except README.win32) as best I can tell. It's
just a little annoying to me to expect a text file and get a pod file.
I renamed all of the '.dev' docs to '.pod' a few days ago.
> find -E . -not \( -name .svn -prune \) -type f -not -perm +111 -not
> -regex '.*\.([a-z0-9_]+|C)' -not -name Makefile -not -name harness
> -exec podchecker '{}' \; |& grep -v 'does not contain any pod commands'
This should get everything:
perl -mPod::Find -mFile::Find::Rule -le 'print join "\n", grep !/\.(?:pm|pl|pod|t|pir|pasm|pmc|ops|pbc|dump|c|h)$/, File::Find::Rule->file->exec(sub {Pod::Find::contains_pod($_[0]) && not -x $_[0]} )->not_name(qw( harness .svn CVS))->in(".")'
Note: Pod::Parser prior to 1.34 (or maybe 1.33 - I can't remember when
I submitted the patch) will miss some valid pod files
> seems to find them all(except README.win32) as best I can tell. It's
> just a little annoying to me to expect a text file and get a pod file.
I agree. The obvious candidates are:
README.win32
compilers/pge/README
compilers/pge/P6Rule.grammar (-> P6Rule_grammar.pod?)
docs/BROKEN
docs/ROADMAP
tools/util/smokeserv-README
src/dynclasses/README
languages/LANGUAGES.STATUS
languages/tcl/README
I'm happy to make these changes if there are no objections.
Cheers,
-J
--