Hello, Sorry for the late of reply, I just solve it yesterday. It's
because a module of mine is using the global variable
our @array = ();
When I migrate from CGI to mod_perl, I forgot to fix that. Now I just
understand that because mod_perl only compile once, and the subsequent
execution of
On Tue, Jun 24, 2008 at 9:07 AM, william [EMAIL PROTECTED] wrote:
Before asking here, I had read a few articles in perl.apache.org about
caching issue in mod_perl, but I still don't get it right with my
program when I had already changed the input, it still giving me the
result of old input.
Hello,
Before asking here, I had read a few articles in perl.apache.org about
caching issue in mod_perl, but I still don't get it right with my
program when I had already changed the input, it still giving me the
result of old input. I aware that the child process will only compile
the code for
I like to add on something, I had put the pragma
use strict;
use warnings;
on all modules that I had, but I didn't get the warnings of Variable
$foo will not stay shared at... .
What other possibility that might cause my program to cache the result
even when the input has already changed ?
william wrote:
I like to add on something, I had put the pragma
use strict;
use warnings;
on all modules that I had, but I didn't get the warnings of Variable
$foo will not stay shared at... .
What other possibility that might cause my program to cache the result
even when the input has
Thank you for the reply,
That's one of the articles that I had read, but still I have not found
where my code having the my scoped variable in nested subroutines ,
I also aware of the nature of ModPerl::Registry would handle the code
in its subrountine called handle. I have used global variable
