I also noticed that if a module has a corresponding POD file (for example: POSIX.pm and POSIX.pod) the description is in the POD file and won't get picked up at all. I applied this patch which seems to fix this (it also prevents POSIX.pm from appearing twice in the resulting list):
202,204c202,206
< return unless /\.p(?:m|od)\z/;
< s/\.pod\z/.pm/; # if it's POD, parse t
+he corresponding code
< return if not -f;
---
> return unless -f and /\A(.+)\.pm\z/;
> my $module = $1;
> my $version = get_module_version( "$mo
+dule.pm" ) || -e "$module.pod" && get_module_version(
+ "$module.pod" );
> my $desc = get_module_description(
+"$module.pm", $opt_limit ) || -e "$module.pod" && get_module_descript
+ion( "$module.pod", $opt_limit );
>
207,209c209,211
< get_module_version( $_ ),
< get_module_description( $_, $o
+pt_limit ),
< $opt_path ? $File::Find::name
+: undef,
---
> $version,
> $desc,
> $opt_path ? $File::Find::name
+: undef
HTH
-
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 How to display code and escape characters
are good places to start.
|