James G Smith <[EMAIL PROTECTED]> said something to this effect on 07/03/2001:
> darren chamberlain <[EMAIL PROTECTED]> wrote:
> > James G Smith <[EMAIL PROTECTED]> 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.
