Sorry for a little off-thread.
What will happen if I use shared library
generated by SWIG when it's updated but
perl module, which is just a wrapper, doesn't
changed. Does Apache::StatINC.pm will take care ?
Do I need just 'touch' perl module.
regards,
On Mon, 27 Mar 2000, Ask Bjoern Hansen wrote:
[...]
> > setting a variable with PerlSetVar would change it to what we have
> > proposed.
>
> Or maybe it could try the other if the first doesn't work. (Except that
> might get very confusing.. hmn).
Sorry about following up to my own message.
Ma
On Tue, 28 Mar 2000, René Seindal wrote:
> If both ways cause problems, then the right solution is to leave it to
> the user. Apache::StatINC already uses dir_config() to adjust its
> behaviour according to user preferences, so adding another configuration
> variable can't be a problem. Current
Ken Williams wrote:
>
> [EMAIL PROTECTED] (René Seindal) wrote:
> >I just got bitten by the problem of Apache::StatINC not reloading
> >modules found through an element of @INC, which is no longer present
> >when StatINC runs.
> [...]
> >A small change to StatINC solves the problem. Since StatINC
[EMAIL PROTECTED] (René Seindal) wrote:
>I just got bitten by the problem of Apache::StatINC not reloading
>modules found through an element of @INC, which is no longer present
>when StatINC runs.
[...]
>A small change to StatINC solves the problem. Since StatINC could stat
>the file, the file is
I just got bitten by the problem of Apache::StatINC not reloading
modules found through an element of @INC, which is no longer present
when StatINC runs. This happens when a module adds a private directory
to @INC, which is then reset by mod_perl after the request is done.
This problem is mention
