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
%+ not scoped properly #15638
Comments
From @nkhCreated by @nkhHi, based on perlre: These special variables, like the %+ hash and the numbered match variables the following code parse a string which has the form {block1}* text* I use named capture (b1, b2) to capture the blocks. for each test case the following is display test case
The problem can already be seen within the first iterations where $+{b1} adding an extra block fixes the problem for (qw( $args =~ s/^ (?'b1' (?:\{[^\{\}]*\}) ) //x ; $args = reverse $args ; $args =~ s/^ (?'b2' (?:\}[^\{\}]*\{) ) //x ; my $t = reverse $args; print "-----------------\n\n" ; Perl Info
|
From @iabynOn Fri, Sep 30, 2016 at 05:51:27PM -0700, nadim khemir wrote:
This is intended behaviour. From the point of view of the dynamic scope A similar effect can be seen with this simplified program: for (qw(ab XY)) { which outputs: PRE: [][] PRE: [a][b] Adding an extra scope like for (qw(ab XY)) { will cause the output to change to: PRE: [][] PRE: [][] -- |
The RT System itself - Status changed from 'new' to 'open' |
From @nkhA hint in the documentation would be nice :) maybe with this example On Mon, Oct 3, 2016 at 12:09 PM, Dave Mitchell via RT <
|
Migrated from rt.perl.org#129771 (status was 'open')
Searchable as RT129771$
The text was updated successfully, but these errors were encountered: