Re: tracking down why a module was loaded?;

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? A.pm: - package A; use Carp (); BEGIN { Carp::cluck("I don't want to wake up!!

Re: tracking down why a module was loaded?;

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::

Re: tracking down why a module was loaded?

Thanks for the hint. It worked perfectly. I didnt connect Cluck, and BEGIN. doh. nobody spotted the unintended irony in my question .. perl-status itself (Apache::Status) was the one pulling in CGI.pm !! Turns out, if you load Apache::Request before Apache::Status, it uses that instead of the (l

Re: tracking down why a module was loaded?;

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; # becau

Re: tracking down why a module was loaded?;

On Fri, 15 Sep 2000, Stas Bekman wrote: > 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 w

Re: tracking down why a module was loaded?;

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? override the builtin require with CORE::GLOBAL::require. something like the below

Re: tracking down why a module was loaded?;

Doug MacEachern wrote: > > modperl is the best kept secret on the net. Shame! > seems to generate plenty of list traffic for a "secret" ;) Don't you all think, that mod_perl isn't promoted enough and this will kill it someday, despite its technical goodness? - There are no articles in the "main

Re: tracking down why a module was loaded?;

At 10:28 PM 9/26/2000 +0200, Alexander Farber (EED) wrote: >Doug MacEachern wrote: > > > modperl is the best kept secret on the net. Shame! > > seems to generate plenty of list traffic for a "secret" ;) > >Don't you all think, that mod_perl isn't promoted enough and >this will kill it someday, des

Re: tracking down why a module was loaded?;

Gunther Birznieks wrote: > I unfortunately have to agree. > > And in the end, the salaries for mod_perl programmers > are pretty high right now because of it -- so will a system really cost > less to develop in mod_perl than in Java if Java programmers are becoming > less expensive than mod_per

Re: tracking down why a module was loaded?;

OTECTED]>Time 20:50 Copy to[EMAIL PROTECTED] (bcc: Simon Wilcox/BASE/WilliamsLea) Bcc Simon Wilcox/BASE/WilliamsLea Fax to Subject Re: tracking down why a module was loaded?; Gunther Birznieks wrote: > I unfortunately have to agree. >

Re: tracking down why a module was loaded?;

On Wed, 27 Sep 2000, Gunther Birznieks wrote: > At 10:28 PM 9/26/2000 +0200, Alexander Farber (EED) wrote: > >Doug MacEachern wrote: > > > > modperl is the best kept secret on the net. Shame! > > > seems to generate plenty of list traffic for a "secret" ;) > >Don't you all think, that mod_perl isn

Re: tracking down why a module was loaded?;

On Wed, 27 Sep 2000, Matthew Byng-Maddick wrote: > > We all have to do our part to evangelize mod_perl more. I think ISPs are > > really key here as I think I may have mentioned before. If you get the ISPs Actually I think the people we need to get involved are the web site builders - the larg

Re: tracking down why a module was loaded?;

On Wed, 27 Sep 2000, Matt Sergeant wrote: > On Wed, 27 Sep 2000, Matthew Byng-Maddick wrote: > Actually I think the people we need to get involved are the web site > builders - the larger companies offering dynamic web content creation. We > also need some more mainstream tools, the oft-requested

Re: tracking down why a module was loaded?;

Matt Sergeant wrote: > > On Wed, 27 Sep 2000, Matthew Byng-Maddick wrote: > > > > We all have to do our part to evangelize mod_perl more. I think ISPs are > > > really key here as I think I may have mentioned before. If you get the ISPs > > Actually I think the people we need to get involved ar