None of the command and identifier should work with a binvar named with only the '&' sign, just like '%' shouldn't be allowed in normal variables routines.
The $regsubex issue may or may not be a bug
Spaced out [ ] will be evaluated before the identifier itself is, so there's no problem with $1 there.
Non spaced out [ ] won't be evaluated before the identifier but when the identifier is parsing its parameters.. except in $regsubex:
It is known that the replacement parameter is not evaluated in $regsubex until the regex matches have been done and replacement occurs and that $N- are used to store markers such as \n.
Here the parameter is not the replacement but it looks like $regsubex is also not evaluating the parameter until it is replacing, which may not be that useful, but in fact it may allow one to store each replacement into a different variables this way, which may have been intended, and the fact that $1 is $null could come from the fact that $1- is restored when $regsubex finishes, before it was the last parameter so it was only a problem there, but yeah now you would have to watch out for the output param as well.
I believe none of the binvar '&' usage being allowed can be changed at this point, just like '%' can't, but it's so bad that i'd still like to see this fixed, all of it.
Last edited by Wims; 07/09/19 04:52 PM.
