"x" =~ / [\x{1234}] /x for 0 .. 100_000; "x" =~ /(?: \x{1234} | \x{1234} )/x for 0 .. 100_000; "\x{4321}" =~ / \x{1234} /x for 0 .. 100_000;
Curious, the bug doesn't bite if character is put in a class or dummy alternation. Most important, there's no bug if target string is utf8 itself. That's why, I think, it wasn't found sooner. Unicode in regexes most often means Unicode in texts.
In reply to Re: Memory leak in unicode substitution
by vr
in thread Memory leak in unicode substitution
by am12345
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |