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?
Advertising
So it might be a general problem with the way that *code blocks inside regexes* access outer lexicals. (It doesn't happen with code blocks *outside* of regexes, and as the other ticket demonstrates, also doesn't happen inside the regex-portion of regexes.)
