According to "C. Chad Wallace" <cwall...@lodgingcompany.com> on Thu, 05/27/10 at 18:41: > > Actually, no. %INC only lists modules that have been loaded into the > current instance, "via the 'do', 'require', or 'use' operators."[1]
Okay, my ignorance of %INC is showing. Thanks. > The only extraneous stuff it includes is the pragmas (strict, features, > warnings, etc.) but those are easily excluded because of their > all-lowercase names. I agree - not a problem., > Now that Hendrik mentioned it, it seems to me that %INC is probably your > best bet. But what you would have to be sure of, in the script that > loads your module to dump %INC, is that you also run your module through > its paces to be sure that all dependencies are loaded--even if some are > "require"d instead of "use"d--before you dump %INC. > > [1] see the %INC entry in perlvar. I have had to go back to the docs time and again to get the two straight in my head (USE and REQUIRE) since they evolved over time and I never did much module or package coding until recently. What I think you are saying is that once all/most of my code paths are traversed, then all/most of the associated modules will be part of %INC for me to try Hendrick's suggestion. I'd liken it to blowing up a kid's balloon just to see what is written on the surface of the rubber which is hard to read with the balloon is deflated. Of course, unlike here, one has to be careful not to inflate the balloon too much or bad things happen... ;-) I have several great suggestions now to try. Thanks! Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template ----------------------------------------->|
