You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by James G Smith <JG...@TAMU.Edu> on 2001/07/03 16:22:01 UTC

Re: RFC: Logging used Perl Modules (was Re: API Design Question)

darren chamberlain <dl...@users.sourceforge.net> wrote:
>James G Smith <JG...@TAMU.Edu> said something to this effect on 07/02/2001:
>> How would something like this do:
>> 
>> NAME
>> 
>> Apache::Use
>> 
>> SYNOPSIS
>> 
>> use Apache::Use (Logger => DB, File => "/www/apache/logs/modules");
>> 
>> DESCRIPTION
>> 
>> Apache::Use will record the modules used over the course of the 
>> Perl interpreter's lifetime.  If the logging module is able, the 
>> old logs are read and frequently used modules are automatically 
>> loaded.  Note that no symbols are imported into packages.
>
>You can get this information from %INC, can't you? e.g.:

Most definitely.  However, you lose information about which 
modules are needed more often than others.  There's no difference 
between all scripts needing CGI.pm and one script needing 
Foo::Bar.  

We also lose timing information.  If 90% of the modules are 
loaded into the process with the last request before the child is 
destroyed, there's no point in loading them during the 
configuration phase.  We can help this a little by taking 
snapshots of %INC at regular intervals (at the end of each 
request, for example).

The current code I have uses %INC, but I wanted to write
something like the following:

sub use : immediate {
  # do stuff here if logging
  return CORE::use(@_);
}
-- 
James Smith <JG...@TAMU.Edu>, 979-862-3725
Texas A&M CIS Operating Systems Group, Unix

Re: RFC: Logging used Perl Modules (was Re: API Design Question)

Posted by Robin Berjon <ro...@knowscape.com>.
On Tuesday 03 July 2001 16:46, darren chamberlain wrote:
> James G Smith <JG...@TAMU.Edu> said something to this effect:
> > The current code I have uses %INC, but I wanted to write
> > something like the following:
> >
> > sub use : immediate {
> >   # do stuff here if logging
> >   return CORE::use(@_);
> > }
>
> To go OT here, what would 'immediate' be doing here, if Perl
> supported it?

It would run, well, immediately :) C<use> is run before the rest of the code 
(apart from BEGIN blocks) which is why one can't overload it (now) iirc.

-- 
_______________________________________________________________________
Robin Berjon <ro...@knowscape.com> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
In which level of metalanguage are you now speaking?


Re: RFC: Logging used Perl Modules (was Re: API Design Question)

Posted by darren chamberlain <dl...@users.sourceforge.net>.
James G Smith <JG...@TAMU.Edu> said something to this effect on 07/03/2001:
> darren chamberlain <dl...@users.sourceforge.net> wrote:
> > James G Smith <JG...@TAMU.Edu> said something to this effect on 07/02/2001:
> > > Apache::Use
> >
> > You can get this information from %INC, can't you? e.g.:
> 
> Most definitely.  However, you lose information about which 
> modules are needed more often than others.  There's no difference 
> between all scripts needing CGI.pm and one script needing 
> Foo::Bar.  

Good point.

> We also lose timing information.  If 90% of the modules are 
> loaded into the process with the last request before the child is 
> destroyed, there's no point in loading them during the 
> configuration phase.  We can help this a little by taking 
> snapshots of %INC at regular intervals (at the end of each 
> request, for example).
> 
> The current code I have uses %INC, but I wanted to write
> something like the following:
> 
> sub use : immediate {
>   # do stuff here if logging
>   return CORE::use(@_);
> }

To go OT here, what would 'immediate' be doing here, if Perl
supported it?

(darren)

-- 
The three most dangerous things are a programmer with a soldering
iron, a manager who codes, and a user who gets ideas.

Re: RFC: Logging used Perl Modules (was Re: API Design Question)

Posted by Doug MacEachern <do...@covalent.net>.
On Tue, 3 Jul 2001, James G Smith wrote:
 
> The current code I have uses %INC, but I wanted to write
> something like the following:
> 
> sub use : immediate {
>   # do stuff here if logging
>   return CORE::use(@_);
> }

you could just override CORE::GLOBAL::require.  you don't need to
override the import, and your version of require will be called at the
same time as the 'use'.