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)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.