[perl #131870] [CONC] [REGEX] Capture lookup inside regex is not threadsafe

2018-03-11 Thread Jan-Olof Hendig via RT
On Wed, 09 Aug 2017 13:32:58 -0700, sml...@gmail.com wrote: > Heh, on further thought, they may be the same issue after all. > > In `/(...) { ... $i ... $0 ... }`, both the $i and the $0 (or $/ > rather) are outer lexicals from the point of view of the curly block, > right? > > So it might be

[perl #131870] [CONC] [REGEX] Capture lookup inside regex is not threadsafe

2017-08-09 Thread Sam S. via RT
Heh, on further thought, they may be the same issue after all. In `/(...) { ... $i ... $0 ... }`, both the $i and the $0 (or $/ rather) are outer lexicals from the point of view of the curly block, right? So it might be a general problem with the way that *code blocks inside regexes* access

[perl #131870] [CONC] [REGEX] Capture lookup inside regex is not threadsafe

2017-08-09 Thread Sam S. via RT
Also notable is that multiple iterations somehow see the same value for `$i` (as observed in the output listing above). I've sumbitted a separate issue for that (RT #131871), because the Capture-lookup bug of the current issue occurs even when removing the `$i`.