On Wednesday, 28 September 2011 00:46:51 Marco Walther wrote:
> Do you have any idea where I might start looking? I don't have much
> insight into the Perl or mod_perl internals, but I played which large
> C-based packages before;-)
I have seen your mail on the user's list. My first thought had
Thanks a lot for your good explaining.I have been somewhat clear about it.
I'll do more reading just as you said.:)
Angel Flower
From: Perrin Harkins <[EMAIL PROTECTED]>
To: angel flower <[EMAIL PROTECTED]>
CC: "modperl@perl.apache.org"
Subject: Re: a new mod
[ Please keep your questions on the list. ]
On Wed, 2005-10-19 at 12:39 +0800, angel flower wrote:
> hi,perrin,
> Can you tell me what meaning of this sentence:
>
> Making a sub that refers to a lexical variable declared outside of its
> scope will ALWAYS create a closure.
>
> Why this happen?
angel flower wrote:
> With mod_perl, each subroutine in every Apache::Registry script is
> nested inside the handler subroutine.
That's true, but it didn't contribute to your problem. What Stas was
referring to in that writeup was a sub that is already nested before you
run it under Apache::Regi
hn ORourke" <[EMAIL PROTECTED]>
To: "Perrin Harkins" <[EMAIL PROTECTED]>
Cc: "angel flower" <[EMAIL PROTECTED]>;
Sent: Tuesday, October 18, 2005 11:33 PM
Subject: Re: [OT] Re: a new mod_perl problem
> Perrin Harkins wrote:
>
> >
> >Good guess,
vars with 'my' outside of nested subroutine,the
problem happened.That's the reasons.
Thanks for everyone answerer.
Angel Flower
From: "angel flower" <[EMAIL PROTECTED]>
To: modperl@perl.apache.org
Subject: a new mod_perl problem
Date: Tue, 18 Oct 2005 17:38:17
Perrin Harkins wrote:
Good guess, but that's not what is happening here. What our flowery
friend has stumbled onto is a closure. When a subroutine references a
"my" variable that was declared outside of that subroutine's scope, the
sub will keep a private copy of that variable. If it wasn't
On Tue, 2005-10-18 at 11:01 +0100, John ORourke wrote:
> 'my' means that it is local to the main program, so your subroutine
> won't see that version of "$counter". Your subroutine will create and
> access a global version of "$counter" which is separate and doesn't get
> re-initialised.
Good gues
angel flower wrote:
>
> Thanks.But I think your answer is not the one that I wanted.
http://perl.apache.org/docs/1.0/guide/porting.html#Sometimes_it_Works__Sometimes_it_Doesn_t
http://perl.apache.org/docs/general/perl_reference/perl_reference.html#myScoped_Variable_in_Nested_Subroutines
HT
Thanks.But I think your answer is not the one that I wanted.
From: John ORourke <[EMAIL PROTECTED]>
To: angel flower <[EMAIL PROTECTED]>
CC: modperl@perl.apache.org
Subject: [OT] Re: a new mod_perl problem
Date: Tue, 18 Oct 2005 11:01:47 +0100
Angel Flower,
'my' mea
Angel Flower,
'my' means that it is local to the main program, so your subroutine
won't see that version of "$counter". Your subroutine will create and
access a global version of "$counter" which is separate and doesn't get
re-initialised.
You need to read up on 'my' and references - do "man perl
hi,
I am new to mod_perl.This is my first doubt,and I need some help.
I test this script under mod_perl:
#!/usr/bin/perl -w
use strict;
use warnings;
print "Content-type: text/plain\r\n\r\n";
my $counter = 0; # Explicit initialization technically redundant
for (1..5) {
incremen
Hello budddy, I am new to modperl too but i think you have to specify a
loadmodule as
LoadModule perl_module modules/mod_perl.so
Then it will recognise all the modperl directives. Perhaps that might help.
With warm regards.
Vivek J. Joshi.
[EMAIL PROTECTED]
Trikon electronics Pvt. Ltd.
-
I am new to mod_perl. I installed mod_perl version 1.29 with apache
1.3.33, and created the following section under apache httpd.conf:
SetHandler perl-script
PerlHandler Apache::Registry
Options +ExecCGI
PerlSendHeader On
Allow from all
When I run http://hostnamer/perl/ from
Gert Jan Schipper wrote:
-8<-- Start Bug Report 8<--
1. Problem Description:
After make install I get the following error:
/usr/bin/perl -Iblib/lib -I/tmp/mod_perl-2.0.0-RC5/Apache-Test/lib
-MModPerl::BuildMM -e ModPerl::BuildMM::glue_pod
ModPerl-Re
-8<-- Start Bug Report
8<--
1. Problem Description:
After make install I get the following error:
/usr/bin/perl -Iblib/lib
-I/tmp/mod_perl-2.0.0-RC5/Apache-Test/lib -MModPerl::BuildMM -e ModPerl::BuildMM::glue_pod
ModPerl-Registry/lib/ModPe
On Tue, 2004-01-27 at 17:10, Rafael Caceres wrote:
> But while 5.8.0 compiles clean (after a LANG=;export LANG), trying to
> get 5.8.1, 5.8.2 and 5.8.3 to compile on Red Hat 9 (gcc 3.2.2-5 and
> glibc 2.3.2-27.9.7) with:
> sh Configure -de
> make
> make test
>
> fails on test 17 at lib/Time/Local
On Tue, 2004-01-27 at 11:24, Perrin Harkins wrote:
>
> > Seems like a lot of upgrading just to
> > go from 5.8.0 to 5.8.1, but I guess a lot of bug fixes
> > and enhancements were added.
>
> There were a few. The one that mattered the most to me is that the
> locale issues are fixed so that you
On Tue, 2004-01-27 at 11:16, Mike NoLast wrote:
> Thanks. As noted before, that means a major upgrade to
> several components (apache, arp, mod_perl, and so on).
> I guess I can get those components from Fedora and
> give it a whirl.
You need to understand that mod_perl 2 is still undergoing signi
--- Perrin Harkins <[EMAIL PROTECTED]> wrote:
> On Tue, 2004-01-27 at 08:56, Mike NoLast
> wrote:
>
> > rpmbuild --rebuild mod_perl-1.99_07-5.src.rpm
>
> Don't do that; that version is ancient. Use the
> latest. Make your own
> RPM if you nee
On Tue, 2004-01-27 at 08:56, Mike NoLast
wrote:
> rpmbuild --rebuild mod_perl-1.99_07-5.src.rpm
Don't do that; that version is ancient. Use the latest. Make your own
RPM if you need to.
- Perrin
--
Reporting bugs: http://perl.apache.org/bu
I am trying to upgrade perl on a RH 9 Linux system
using Fedora src.rpms.
I built perl and perl_suid from Fedora 5.8.1 src.rpms
without problems and installed same (had to use
--force because the CGI's man and other bundle files
conflict with t
On Thu, 2003-10-30 at 11:41, Mark Hawkes wrote:
> At 11:23 2003-10-30 -0500, you wrote:
> >In my never ending search for more elegant looking and self-documenting
> >code I decided to try out the Switch module.
>
> I've sometimes faked a switch statement like this...
That's a good approach, and
At 11:23 2003-10-30 -0500, you wrote:
In my never ending search for more elegant looking and self-documenting
code I decided to try out the Switch module.
I've sometimes faked a switch statement like this...
SWITCH: {
$foo eq 'r' && do {
# read stuff
last SWITCH;
};
$foo eq 'w' && d
Geoffrey Young wrote:
John Day wrote:
In my never ending search for more elegant looking and
self-documenting code I decided to try out the Switch module. In the
following fragment of code:
#!/usr/local/bin/perl
# AppSys: Manage Profile
use strict;
use CGI qw/:standard/;
use CGI::Carp qw(fa
John Day wrote:
In my never ending search for more elegant looking and self-documenting code I decided to try out the Switch module. In the following fragment of code:
#!/usr/local/bin/perl
# AppSys: Manage Profile
use strict;
use CGI qw/:standard/;
use CGI::Carp qw(fatalsToBrowser);
use Swit
In my never ending search for more elegant looking and self-documenting
code I decided to try out the Switch module. In the following fragment of
code:
#!/usr/local/bin/perl
# AppSys: Manage Profile
use strict;
use CGI qw/:standard/;
use CGI::Carp qw(fatalsToBrowser);
use Switch;
my $cgi = CGI->
27 matches
Mail list logo
