On Thu, Feb 16, 2012 at 16:01, Markus Jansen <markus.jan...@ericsson.com> wrote: > The problems described below don't hurt that much for PAR building, but do > cause lots of overcautious "uses" indications > when trying to build a module dependency graph.
Known problem. M:SD wans't meant to do detailed dependency analysis - just make sure we pack anything that might be required. > Thus, I wonder whether the present Module::ScanDeps parsing touches a wall > (or ceiling) - in other words, whether it would make sense > to deploy the parsing job to e.g. something PPI based. Without a decent > hierarchy tree based view of a Perl module, > parsing might become a nightmare. Sure, knock yourself out :) But I'm not sure if PPI will help much. The real pain is TMTOWTDI when it comes to require'ing other stuff. Heck, besides from the simplistic parsing of Perl source that M:SD does and the trivial recursive scanning strategy, the real value if M:SD lies in the %Preload array. Over the years is acquired detailed knowledge of the arcane ways certain modules try to load others (or require data files to present etc). Cheers, Roderich
