Re: What modules are we actually using?

Actually just looking for the use, require, and do (??) calls may be sufficient. (You use "do" to load CPAN modules?)

Personally, all of the CPAN code I use is used either via 'use Bare::Word' or 'require Bare::Word'. If I were to grep through all of my code for that, uniq that list, and then remove the in-house modules, that would be something I could feed to CPAN. Even if those modules were to require other modules, the CPAN module would handle that for me.

Sometimes, a simple solution with minor manual steps is sufficient ;-)

Comment on Re: What modules are we actually using?

Replies are listed 'Best First'.
Re^2: What modules are we actually using? by cbrandtbuffalo (Deacon) on Apr 28, 2005 at 19:00 UTC
That's basically where I landed too, and the approach I'm going to take. I started looking at Module::Info and it already does the 'use' and 'require' parts. I'm going to try to add: option to exclude pragmata; it currently spits out stuff like 'strict' from 'use strict' as a module search for RootClass, which can be used in DBI connect search for Class::DBIs has_a which can inflate something into an object of a specified class; I know we have the last two items in our code base for sure. As others turn up, I'll add them too.	[reply]

Replies are listed 'Best First'.

Re^2: What modules are we actually using?
by cbrandtbuffalo (Deacon) on Apr 28, 2005 at 19:00 UTC

Module::Info

option to exclude pragmata; it currently spits out stuff like 'strict' from 'use strict' as a module
search for RootClass, which can be used in DBI connect
search for Class::DBIs has_a which can inflate something into an object of a specified class;

I know we have the last two items in our code base for sure. As others turn up, I'll add them too.

[reply]