-
Notifications
You must be signed in to change notification settings - Fork 559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lexical variables in regex code blocks not propagated (SEGFAULT) #2683
Comments
From @Tux--8<--- use strict; my %hash = ( print "\n=== Extract lexical\n"; print "=== Report\n"; print "\n=== Extract global\n"; print "=== Report\n"; === Extract lexical === Extract global where it proves that a lexical $h isn't known inside (?{ $hash{$h}{$1} = $2 }) # perl5.7.0 -V Characteristics of this binary (from libperl): |
From @vanstynIn <20001005152535.33DD.H.M.BRAND@hccnet.nl>, "H.Merijn Brand" writes: Thanks for the report. This is a known problem, and on my list. :( Sarathy: << A particularly difficult aspect of the problem, however, is the our $a = 1; .. it is not at all clear to me what results we should expect, only Hugo |
From @TuxOn Thu 05 Oct 2000 16:26, Hugo <hv@crypt.compulink.co.uk> wrote:
Solved before 5.8?
-- |
From @vanstyn"H.Merijn Brand" <h.m.brand@hccnet.nl> wrote: Unlikely, now. :Still on your list? Yes. Volunteers welcome, though. :) Hugo |
From @TuxOn Wed 27 Feb 2002 21:38, Hugo van der Sanden <hv@crypt.compulink.co.uk> wrote:
If I wave my hands any faster I will lift off
-- |
From @smpeters
I just tried this with bleadperl, and got a coredump for my efforts. |
From @smpeters
#0 0x1c097ac6 in S_varname (gv=0x0, gvtype=36 '$', targ=2, keyname=0x0, |
From @iabynOn Mon, Nov 07, 2005 at 04:14:46PM -0800, Steve Peters via RT wrote:
I think this another instance of "lexical in re_evals are borked". I'll -- |
From @cpansproutThis has been fixed by the commits leading up to eb58a7e. |
@cpansprout - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#4383 (status was 'resolved')
Searchable as RT4383$
The text was updated successfully, but these errors were encountered: