Re: What modules are we actually using?

just a thought: You could walk all your modules and see if the access time of the module files are something recent.

Comment on Re: What modules are we actually using?

Replies are listed 'Best First'.
Re^2: What modules are we actually using? by Booger (Pilgrim) on Apr 27, 2005 at 14:47 UTC
Having tried this sort of thing before, I think that your suggestion is a good one. Figuring out which modules are being used is an extremely difficult task (given that some of your modules may be included at run-time) and even the best solutions for walking a codebase and discovering module usage don't quite cut it.	[reply]
Re^3: What modules are we actually using? by dmorelli (Scribe) on Apr 27, 2005 at 15:02 UTC
I was thinking about this too. It sounds like a tall order. Maybe it's unlikely to be happening in the OP's particular code base, but it's entirely possible to require an arbitrarily-named file that itself is requiring modules and doing things with them. And eval could be used in a similar manner. Hard to say where code may be coming from.	[reply]