Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I wanted to add prunepaths support. This patch includes my changes as well as the patch that jwkrahn posted above.

48,51d47 < =item B<-x>, B<--prunepaths> < < Directories to omit from the search for perl modules. < 191d186 < 'prunepaths|x=s@' => \( my $excludes ), 207,213c202,204 < check_prune($_) && ( $File::Find::prune = 1 ) if $ex +cludes; < < return unless -f and /\A(.+)\.pm\z/; < my $module = $1; < my $version = get_module_version( "$" ) + || -e "$module.pod" && get_module_version( "$module.pod" + ); < my $desc = get_module_description( "$", +$opt_limit ) || -e "$module.pod" && get_module_description( "$module. +pod", $opt_limit ); < --- > return unless /\.p(?:m|od)\z/; > s/\.pod\z/.pm/; # if it's POD, parse t +he corresponding code > return if not -f; 216,218c207,209 < $version, < $desc, < $opt_path ? $File::Find::name : undef --- > get_module_version( $_ ), > get_module_description( $_, $o +pt_limit ), > $opt_path ? $File::Find::name +: undef, 250,254d240 < < sub check_prune { < my $name = shift; < return 1 if grep( /\A$name\z/s, @$excludes ) > 0 and -d $name; < }


Therapy is expensive. Popping bubble wrap is cheap. You choose.

In reply to Re: lspm list names and descriptions of Perl modules in a directory by naChoZ
in thread lspm list names and descriptions of Perl modules in a directory by Aristotle

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (3)
As of 2022-05-22 11:04 GMT
Find Nodes?
    Voting Booth?
    Do you prefer to work remotely?

    Results (80 votes). Check out past polls.