ExtUtils::Installed  provides a standard way to find out what core an
+d module files have been installed.
[download]

#!/usr/bin/perl
use ExtUtils::Installed;

my ($inst) = ExtUtils::Installed->new();
my (@modules) = $inst->modules();

foreach (@modules) {
print $_, ' v', $inst->version($_), "\n";
}
[download]

That is an elegant solution. I used to use all kinds of find and greps and perl one liners... I have added this to my bashrc. It makes me wonder what else I'm missing. Hrm, except that I see below it doesn't find everything.

And looking at the src for the package, it'd not be easy to inherit E::I and extend new() to include more dirs — it's just not set up for that. Sad really.

-Paul

ExtUtils::Installed also has version() so modifying it for your needs shouldn't be difficult. From the docs, it also says

This returns a list of the names of all the installed modules. The perl 'core' is given the special name 'Perl'

Module::CoreList keeps track of what version of perl each module became core which may be of some use as well.

Beware: ExtUtils::Installed doesn't list all modules.

I've used Pod::Webserver to display a list of all the modules that are installed in my browser, including any bespoke ones that aren't from CPAN.

--

Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)

rinceWind,
Good to know. It appears demerphq is the current maintainer and there are 15 current bugs in RT.

Cheers - L~R

perl -e 'while (<@INC>) { while (<$_/*.pm>) { print "$_\n"; } }'
[download]

That's a bit too simplistic: it will miss things like File::Find ($_/File/Find.pm).
"What should it profit a man, if he should win a flame war, yet lose his cool?"

monkfan,
Not only does your code not do what was asked for, I think it is broken. I believe both uses of glob in your while loop lead to infinite loops. I can't be sure as I don't have access to perl currently. Update: tye informed me this does work. This is because glob in scalar context doesn't create an iterator, it is an iterator. After re-reading I/O Operators in perlop I realized I was mistaken. I would still recommend spelling out glob over angle brackets to avoid confusion with readline.

Update 2: I am not sure why, but this still seems odd to me. Perhaps it is because I have less than 30 hours to wait before starting a 3 week vacation. I wonder how the following two examples would behave (i.e. how they are scoped):

while (my $file = next_file()) {
    print "$file\n";
}
sub next_file { <*> }
[download]

while (my $file = next_file()) {
    print "$file\n";
    my $next = <*>;
    last if ! defined $next;
    print "$next\n";
}
sub next_file { <*> }
[download]

Cheers - L~R