> > > What is the best way to define a global value like $query if I want to
> > > 'use strict'. I really don't want to be passing $query to all my
> > > subroutines. I could package define it as $main::query but that seems
> > > awkward.
> "perldoc perlref" addresses the nested subroutine prob
as if it were a subroutine named
printQueryParams.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 14, 2000 3:44 AM
To: Stas Bekman
Cc: Jie Gao; [EMAIL PROTECTED]
Subject: Re: Problem with form data using mod_perl and CGI.pm
Stas Bekman wrote:
>
Stas Bekman wrote:
>
> On Mon, 14 Aug 2000, stevenl wrote:
>
> > Thanks. That seems to be the problem, accessing an outer lexical
> > variable in an inner subroutine. I'm not quite sure I understand why
> > Perl behaves this way. Java seems to handle this just fine with the
> > expected behav
On Mon, 14 Aug 2000, stevenl wrote:
> Thanks. That seems to be the problem, accessing an outer lexical
> variable in an inner subroutine. I'm not quite sure I understand why
> Perl behaves this way. Java seems to handle this just fine with the
> expected behavior.
Because Perl != Java. And yo
Thanks. That seems to be the problem, accessing an outer lexical
variable in an inner subroutine. I'm not quite sure I understand why
Perl behaves this way. Java seems to handle this just fine with the
expected behavior.
I'm currently using:
use CGI;
my $query = new CGI();
What is the best w
On Sat, 12 Aug 2000, stevenl wrote:
> I am running Linux 2.2, Apache 1.3.12, mod_perl 1.24, and CGI.pm 2.70.
>
> If I declare a CGI variable using 'my' (see below) and use mod_perl, I
> encounter problems with POST data. On subsequent entries in the form,
> it continues to use the old data.
>
