Re: Re: (?{...code..}) regex construct causing panic: top

That is a good answer, but I think perl should not panic in this case, but point out the problem.

-Mark

Comment on Re: Re: (?{...code..}) regex construct causing panic: top_env in 5.8.2

Replies are listed 'Best First'.
Re: Re: Re: (?{...code..}) regex construct causing panic: top_env in 5.8.2 by BrowserUk (Patriarch) on Feb 25, 2004 at 03:55 UTC
Agreed. And under normal code conditions it does. `{ my $x; { local $x = 1 } }; Can't localize lexical variable $x at (eval 2) line 1, <> line 3.` [download] Putting my "guess the reason" hat on, I could be that they try to keep the regex engine fast and so the error reporting from code blocks in regexes is lighter than elsewhere. Alternatively, it could be just that noone has raised the perlbug to casue it to get fixed yet. Examine what is said, not who speaks. "Efficiency is intelligent laziness." -David Dunham "Think for yourself!" - Abigail Timing (and a little luck) are everything!	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re: Re: (?{...code..}) regex construct causing panic: top_env in 5.8.2
by BrowserUk (Patriarch) on Feb 25, 2004 at 03:55 UTC

Agreed. And under normal code conditions it does.

{ my $x; { local $x = 1 } };
Can't localize lexical variable $x at (eval 2) line 1, <> line 3.
[download]

Putting my "guess the reason" hat on, I could be that they try to keep the regex engine fast and so the error reporting from code blocks in regexes is lighter than elsewhere. Alternatively, it could be just that noone has raised the perlbug to casue it to get fixed yet.

Examine what is said, not who speaks.

"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
Timing (and a little luck) are everything!

[reply]
[d/l]