in reply to Was a module use'd or require'd?
I think it would be more useful as a debugging aid to not produce results in terms of use. One not-uncommon mistake is getting the order of execution wrong. So instead of trying to output what the module looks like on disk, output something more informative.
Output the order in which each require actually happened and the order in which each import() happened (with what arguments). I think I'd actually hook this via the debugger trace mechanism so you can output the order in which each statement was executed followed by the decompiled subroutines that existed when the require finished and then when import() finished.
- tye
In Section
Seekers of Perl Wisdom