# from Nadim Khemir # on Wednesday 09 May 2007 10:51 pm: >PAR has a module to find module dependencies. That might help.
That would be Module::ScanDeps. Needs tests. The static scanning is not using PPI, and I think everyone involved at this point agrees that it should. There is also a lot of "x implies y" dependency chain knowledge encapsulated in there that could stand to be in a data file or somehow configurable+compartmentalized. The compile/run-time scanning is essentially sound in that it dumps %INC, though that leaves you without any knowledge of who required it. The dynamic library list capture is neat too. Also see Devel::TraceDeps, which is currently lacking a frontend (or really, anything to do with interface.) http://scratchcomputing.com/svn/Devel-TraceDeps/trunk I'm trying to enable separating the "we require" from "they require", the idea being that you can "-MDevel::TraceDeps=something" when running the test suite and get recursive comprehensive dependency coverage which would be as thorough as your test coverage. But, I'm lacking tuits right now, so please feel free to steal it and finish it :-D --Eric -- Issues of control, repair, improvement, cost, or just plain understandability all come down strongly in favor of open source solutions to complex problems of any sort. --Robert G. Brown --------------------------------------------------- http://scratchcomputing.com ---------------------------------------------------
