dules that use lazy loading
(eval(require "module.pm")). Somehow @INC gets reset. My errorlog then
states it can't find the required module. Weird thing is, it happens
infrequently.
Anyone that had a similar problem and found a solution? Thanks in
advance :-)
--
Christiaan Kras
Yes,
Because in my error messages it clearly says it can't find the modules
in @INC. Then it shows all the paths in @INC and my custom lib isn't set
there, instead, @INC is at it's original state.
Christiaan Kras
Perrin Harkins schreef:
On 7/6/07, Christiaan Kras <[EMAIL
Perrin Harkins schreef:
On 7/7/07, Christiaan Kras <[EMAIL PROTECTED]> wrote:
Because in my error messages it clearly says it can't find the modules
in @INC. Then it shows all the paths in @INC and my custom lib isn't set
there, instead, @INC is at it's original state.
Perrin Harkins schreef:
On 7/11/07, Christiaan Kras <[EMAIL PROTECTED]> wrote:
I add to @INC with " use lib qw(/my/path) ". All the other modules I
load continue to work fine. Just those that use lazy loading fail
infrequently.
Okay, I think I see the problem. When you chan
Perrin Harkins schreef:
On 7/11/07, Christiaan Kras <[EMAIL PROTECTED]> wrote:
Thanks. I will try that. So basicly, the modules that are loaded at the
first request will stay in memory, but @INC will get reset?
Yes. It's a simulation of CGI behavior. The only reason your CGI
sc
Perrin Harkins schreef:
On 7/11/07, Christiaan Kras <[EMAIL PROTECTED]> wrote:
By the way, I've used push() to add my path to @INC before. But that
didn't work out.
It should work fine. The reason people typically use unshift for this
is that it lets modules in your local pa
ability to do so.
I must add that I'm on a shared server though.
--
Christiaan Kras
