in reply to Re^2: non-capture mode sometimes erases previous capture
in thread non-capture mode sometimes erases previous capture

If you want to keep the captured bits, assign them to variables in your code, rather than relying on them being retained in global variables:

my( $bit1, $bit2, $bit3 ) = /(..)(..)(..)/;

Any code you call -- library routines etc. -- after you run the regex, but before you want to use its results, might also use the regex engine and overwrite those temporary global variables. So, don't rely on it.

(Also, whether any of us agree with you or not, its been that way a very long time and isn't likely to change; so best get used to the idea :) )


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". The enemy of (IT) success is complexity.
In the absence of evidence, opinion is indistinguishable from prejudice. Suck that fhit

Replies are listed 'Best First'.
Re^4: non-capture mode sometimes erases previous capture
by choroba (Archbishop) on May 30, 2018 at 11:01 UTC
    > Any code you call -- library routines etc. -- after you run the regex, but before you want to use its results, might also use the regex engine and overwrite those temporary global variables

    Invoking the regex engine in a different scope doesn't matter, the variables are properly dynamically scoped:

    #!/usr/bin/perl use warnings; use strict; use feature qw{ say }; sub call_me { "xyz" =~ /(..)/; say $1; } "abc" =~ /(.)/; call_me(); say $1; # Still "a".

    Which doesn't mean I recommend using them.

    ($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord }map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,