in reply to Module Subs and Methods

I disagree that simply listing names increases a module's usability. Good examples of how to use the subs - now that is useful. But if it's a list of subs you want, you can use the following *NIX one-liner:
perl -MDevel::Symdump -le'eval"require $ARGV[0]";print for Devel::Symd +ump->new($ARGV[0])->functions' HTML::Parser
UPDATE: or this (more) complete script:
use strict; use warnings; use Devel::Symdump; my $class = shift || die "need module name"; eval "require $class"; my $obj = Devel::Symdump->new($class); print $_,$/ for $obj->functions;
Don't forget that some CPAN author's follow the convention of prepending underscores to 'private' subs - you can filter those out easily with grep:
print $_,$/ for grep ! /::_/, $obj->functions;
should do the trick.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)