It turns out that the problem is related to the recently added regex feature
No, the problem is using a regex to match a literal string without telling it that this is what you wanted to do! The recent \p regex addition just made these bugs more noticeable.
If you ever see a regex with $var in it, you should suspect that \Q$var\E is what should have been used. Looking through Config.pm, I only find one (uncommented) case of this mistake, but it is probably fine since the $var in that case should only contain letters.
So are you the one coding regexen incorrectly this way? If so, the solution is quite simple. If you replace m!$rootb/(.*)/(\w+)\.p.+$!i; with m!\Q$rootb\E/(.*)/(\w+)\.p.+$!i;, for example, then that problem goes away.
Next you have to deal with your misconception that you can use a single character as the directory separator. I suggest you look into File::Spec instead of hand-rolled regexen for comparing paths.
- tye (but my friends call me "Tye")In reply to (tye)Re: Can't find unicode character property definition via main-e or e.pl at unicode/Is/e.pl line 0
by tye
in thread Can't find unicode character property definition via main-e or e.pl at unicode/Is/e.pl line 0
by Rudif
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |