Michael G Schwern wrote:
On Fri, Sep 23, 2005 at 05:38:32PM +0200, Tels wrote:
If you have any ideas how to make this even more usefull, please speak
now. I will have limited email reading/writing capabilities the next two
weeks, but I *will* respond to all emails/critics/praises, even though it
may only be when I return. :)
Is the dependency detector pluggable? The code I'm interested in graphing
requires modules indirectly through things like aliased.pm, base.pm and
Class::Autouse's superloader. It would be nice if I could extend its dep
scanner to take these into account.
I wasn't going to mention it until I had something that actually worked,
but I've got plans to solve this.
I'm aiming for a PPI-based module (most like called Perl::Depends at
this point) that will be properly pluggable, so that additional
Class::Autouse packages and the like can be supported.
I have some _very_ early framework code but nothing useful yet, it's on
the drawing board some time after PPI 1.100 (with the caching code) and
a few other bits and pieces are done.
Adam K
