Re: Preloading Fcntl.pm

2001-12-14 Thread Andrew Green
In article [EMAIL PROTECTED], Stas Bekman [EMAIL PROTECTED] wrote: Andrew Green wrote: The *really* peculiar thing is that actual scripts that use Fcntl work with no problems -- but I can't preload the module, or preload other modules that use it. Hmm, how about upgrading modperl?

Re: Preloading Fcntl.pm

2001-12-11 Thread Andrew Green
In article [EMAIL PROTECTED], Stas Bekman [EMAIL PROTECTED] wrote: Try to call: require Fcntl; instead. Thanks for the tip. I'm afraid the above verbatim produces the following error on restart: | Shutting down http:[ OK ] | Starting httpd: [Mon

Re: Preloading Fcntl.pm

2001-12-11 Thread Stas Bekman
Andrew Green wrote: In article [EMAIL PROTECTED], Stas Bekman [EMAIL PROTECTED] wrote: Try to call: require Fcntl; instead. Thanks for the tip. I'm afraid the above verbatim produces the following error on restart: | Shutting down http:[

Re: Preloading Fcntl.pm

2001-12-11 Thread Andrew Green
In article [EMAIL PROTECTED], Stas Bekman [EMAIL PROTECTED] wrote: Weird, what Perl version are you using? Can you do: perl -MFcntl -le1 or perl -le 'require Fcntl' Both seem to work (producing no output, but no errors either). The *really* peculiar thing is that actual scripts that

Re: Preloading Fcntl.pm

2001-12-11 Thread Jorge Godoy
Stas Bekman [EMAIL PROTECTED] writes: Jorge Godoy wrote: Stas Bekman [EMAIL PROTECTED] writes: I think the general advise is to always call require() and not use() in startup.pl, unless you have a reason for calling certain modules' import() method. Wouldn't that affect mod_perl's

Re: Preloading Fcntl.pm

2001-12-11 Thread Jean-Michel Hiver
Wouldn't that affect mod_perl's advantage of sharing the modules? I mean, would everything be in it's separate namespace and loaded only once for every module as it is with use? I don't know about you guys, but I don't feel that sharing the modules is that much of an advantage. If you write

Re: Preloading Fcntl.pm

2001-12-11 Thread Stas Bekman
Andrew Green wrote: In article [EMAIL PROTECTED], Stas Bekman [EMAIL PROTECTED] wrote: Weird, what Perl version are you using? Can you do: perl -MFcntl -le1 or perl -le 'require Fcntl' Both seem to work (producing no output, but no errors either). The *really* peculiar thing is

Preloading Fcntl.pm

2001-12-10 Thread Andrew Green
I'm trying to use a startup script to preload a selection of common modules, but am having massive problems with Fcntl. If I use Fcntl (); either in the startup script directly or (worse) in any other modules I try to preload, Apache dies silently and immediately upon restart. Checking the

Re: Preloading Fcntl.pm

2001-12-10 Thread Robin Berjon
On Monday 10 December 2001 16:21, Andrew Green wrote: I'm trying to use a startup script to preload a selection of common modules, but am having massive problems with Fcntl. If I use Fcntl (); either in the startup script directly or (worse) in any other modules I try to preload, Apache dies

Re: Preloading Fcntl.pm

2001-12-10 Thread Andrew Green
In article [EMAIL PROTECTED], Robin Berjon [EMAIL PROTECTED] wrote: Have you tried to see if it works without the trailing () ? I have, yes, and I'm afraid it makes no difference. Thanks anyway, Andrew. -- :: article seven Andrew Green automatic

Re: Preloading Fcntl.pm

2001-12-10 Thread Stas Bekman
Andrew Green wrote: In article [EMAIL PROTECTED], Robin Berjon [EMAIL PROTECTED] wrote: Have you tried to see if it works without the trailing () ? I have, yes, and I'm afraid it makes no difference. Try to call: require Fcntl; instead. I think the general advise is to always

Re: Preloading Fcntl.pm

2001-12-10 Thread Jorge Godoy
Stas Bekman [EMAIL PROTECTED] writes: I think the general advise is to always call require() and not use() in startup.pl, unless you have a reason for calling certain modules' import() method. Wouldn't that affect mod_perl's advantage of sharing the modules? I mean, would everything be in

Re: Preloading Fcntl.pm

2001-12-10 Thread Stas Bekman
Jorge Godoy wrote: Stas Bekman [EMAIL PROTECTED] writes: I think the general advise is to always call require() and not use() in startup.pl, unless you have a reason for calling certain modules' import() method. Wouldn't that affect mod_perl's advantage of sharing the modules? I mean,