First of all, I wanted to mention something about the limit, right now we have $maxlenl = 8192, which corresponds to the previous 4096, representing the 'safe' number of character allowed per 'line', shouldn't this number have been used as the limit for $regml* here (but this is also meaningful for others areas)? Which would leave room for handling $regml* value with for example an /echo or whatever, whereas right now, a $regml* value of 8292 characters is very hard to deal with.
The same issue applied to $regml() with 4096, where the longest string could technically have been around 4150. Unfortunately, there is no way to limit all strings to 8192. The maximum string length, with leeway up to 8292, applies to all routine equally. If I did what you are requesting, I would have to arbitrarily choose some routines/identifiers/commands/features to only allow a maxumum of 8192 and others, such as /echo, to allow the leeway up to 8292. That is simply not possible. I would have to make this change, and add checks, in thousands of places for it to make sense.
For all the reasons you mention, even if it were fixed, it would be far from having binvar support for input of regex, this would just be knowing if there's a match.
I think I have found a safe route through the regex code that allows unlimited string length regex matching. As you say, it will only let you know if there's a match. Results would still be truncated. I may include this change in the next beta.
