On Fri, 15 Sep 2000, Matt Sergeant wrote:
> On Thu, 14 Sep 2000, Justin wrote:
>
> > Can anyone tell me the easiest slickest way of determining
> > what was responsible for requesting a module, having discovered
> > that it has been loaded when viewing perl-status?
>
> use OtherPackage; # because you need import to be defined first
> sub OtherPackage::import {
> warn join(':', caller), " tried to load me\n";
> }
Not really. import() is not called for any of these.
use Foo ();
require Foo;
do Foo;
BEGIN{}+cluck in the code or just cluck will do per my original reply.
> Not foolproof, and could cause more damage than good, but sometimes its a
> useful debugging technique.
>
> > modperl is the best kept secret on the net. Shame!
>
> Indeed!
>
> --
> <Matt/>
>
> Fastnet Software Ltd. High Performance Web Specialists
> Providing mod_perl, XML, Sybase and Oracle solutions
> Email for training and consultancy availability.
> http://sergeant.org | AxKit: http://axkit.org
>
>
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://jazzvalley.com
http://singlesheaven.com http://perlmonth.com perl.org apache.org
