Nail down this bug?

[sidki3003]

We can be more exact than "too closely follows". -> "directly follows"
Also mention that we are in capturing stage (vs. replace)?

(This bug is - as whenever already mentioned - probably related to another issue where \X doesn't find anything to capture. So i assume that the here discussed problem only appears when \X is in a similar interim state: Nothing to match after proceeding to the end of expression, but no chance to clean up. However, that would go most likely beyond the scope of this document.)

The examples should show the simple case, and then only variations that show further aspects. I think your example, showing the issue within a global var test, is important.

In the other chapters the term "local variable" is used. I'll replace that with "positional variable".

Code:

-------------------------------------------------------------------------------
2   A capturing positional variable that directly follows a negated expression
    may be incorrectly found to have value in the expressions and filters that
    follow.  To cover this, place positional variables that are next to and
    follow negated expressions in parentheses.

Examples:
(^[a-z])(\0)
(^foo(^bar))(\9)
$TST(foo=(^*bar)(\7))

?