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 upgradi
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
> *re
Jean-Michel Hiver wrote:
>>>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
>> 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 wr
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 aff
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
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:
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
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 modu
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 i
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
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 int
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
13 matches
Mail list logo