Hi Ovid,
Ovid schrieb:
--- Andy Armstrong <[EMAIL PROTECTED]> wrote:
Can anyone think of anything wrong with the approach of replacing
require with an instrumented version? If the consensus is that that's
a sensible approach I'll play with tidying up the code.
You know, that solves an annoying problem I've had with some code which
attempts to rebuild a module's source from what's loaded (very handy
for debugging). I couldn't figure out how to tell what module another
module has loaded, but now it looks like I can :)
Seems like I'm getting into the habit of recommending modules on perl-qa :)
Perhaps http://search.cpan.org/~chromatic/Devel-TraceUse-1.00/ helps here?
I think Eric Wilhelm was hacking on something which extends on this
concept. You know, the MOdule::ScanDeps compile-time and execution-time
dependency scanning could use a make-over.
Best regards,
Steffen
