Re: Wow. Uh. Heh. PerlRun and Seeming Caches...

2004-02-21 Thread Morbus Iff
>> For what it's worth, I had to do this instead: >> >> BEGIN { unshift(@INC, qw(lib extlib)); } > >That's odd, because that's almost exactly equivalent to a "use lib" >call. Are you running this under PerlRun? PerlRun executes BEGIN >blocks every time, but Registry only executes them once. It

Re: Wow. Uh. Heh. PerlRun and Seeming Caches...

2004-02-21 Thread Perrin Harkins
Morbus Iff wrote: For what it's worth, I had to do this instead: BEGIN { unshift(@INC, qw(lib extlib)); } That's odd, because that's almost exactly equivalent to a "use lib" call. Are you running this under PerlRun? PerlRun executes BEGIN blocks every time, but Registry only executes them on

Re: Wow. Uh. Heh. PerlRun and Seeming Caches...

2004-02-21 Thread Morbus Iff
>The only reason it doesn't work the second time is that "use lib 'lib'" >happens at compile time. It's like a BEGIN block. To make it happen >every time, you could just do this: > >unshift(@INC, qw(lib extlib)); For what it's worth, I had to do this instead: BEGIN { unshift(@INC, qw(lib extl

Re: MPM worker and ithreads

2004-02-21 Thread Stefan Cars
Hi! I don't have any problems, I'm just interested in what people think of the performance vs. preforking and if there is any problems using worker and ithreads ? On Fri, 20 Feb 2004, Stas Bekman wrote: > Stefan Cars wrote: > > Hi! > > > > Anyone that has any good links or any good input on usin