Mailing-List: contact embperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (hermes.apache.org: local policy)
Date: Sat, 11 Dec 2004 11:40:50 +1100
Message-ID: <87mzwl8y5p.wl%gus@inodes.org>
From: Angus Lees <gus@inodes.org>
To: wschroed@schroedernet.net
Cc: embperl@perl.apache.org
Subject: Re: session question
In-Reply-To: <1102647924.11021.7.camel@mummer.localhost>
References: <20041209194742.A9889125D27@lnx1.i.ecos.de>
	<1102647924.11021.7.camel@mummer.localhost>
Mail-Followup-To: wschroed@schroedernet.net,
	embperl@perl.apache.org
User-Agent: Wanderlust/2.11.30 (Wonderwall) XEmacs/21.4 (Security Through
 Obscurity)
Mail-Copies-To: never
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII

At Thu, 09 Dec 2004 21:05:24 -0600, Will Schroeder wrote:
> 1: in a pattern match like [$ if ( $fdat{QC} =~ m/(\d+)/  ) $]
> [- $num = $1 -]
> for example. The $1 variable never seems to get populated during the
> match like in a regular old perl script.

aiui, the value of $1, etc variables are "lexically scoped" in perl.

so this should work fine:
[-
  if ( $fdat{QC} =~ m/(\d+)/ ) {
    $num = $1;
  }
-]

whereas your code gets turned into something more like this by
embperl:

 if ( eval { $fdat{QC} =~ m/(\d+)/ } ) {
   eval { $num = $1 };
 }

so $1 loses its value across embperl blocks, in the same way that "my"
variables, etc are also limited to a single embperl block
(ignoring [* *] blocks for the moment).

-- 
 - Gus


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org