Re^4: Repeated code blocks in long and hairy regex

Well, I tried eval because something was already broken. I've removed it now, and have no need for it. I just want my variable to work inside the regular expression. How do I properly quote it, and/or invoke the substitution, so that it will work? I thought this would be easy, but it just did not work as expected. I think the qr// is adding something, because the expression it resolves to is not identical to what I have assigned my variable. But if I use qw// or just q//, those don't seem any better. I just want to drop in a piece of code which looks exactly as I have assigned it to the variable, and, as it happens, I do not need to eval any variables inside my short block of code as there won't be any. So, while simple is the order of the day, it has turned out to be not so simple.

Blessings,

~Polyglot~

Comment on Re^4: Repeated code blocks in long and hairy regex

Replies are listed 'Best First'.
Re^5: Repeated code blocks in long and hairy regex by Corion (Patriarch) on Nov 05, 2023 at 13:58 UTC
I found Regexp::Debugger quite illustrative when trying to find why a regular expression does not match. As you don't show any data for your regular expression and I don't know how Thai is written, I can't conveniently replicate your problem or find why your regexp behaves with your data in a way that you don't want. Maybe you can post relevant data (it is likely to be 6 characters, maybe post them using charnames instead of literals), or find the solution yourself stepping through the matching by using Regexp::Debugger.	[reply]
Re^6: Repeated code blocks in long and hairy regex by Polyglot (Chaplain) on Nov 05, 2023 at 14:18 UTC
I created a small test case for which I was able to "see" what was going on. The qr// quote method does alter the expression, but I did not see why this would have changed the matching. However, the q// did not alter the regex, and it did work as expected in the test substitution. I think I'll be switching to that, and then carefully checking through to see if something else had been inadvertently affected when swapping the code blocks for variables. It seems inevitable that something changed that managed to escape my notice. With nearly 500 lines in the original code, and having swapped out already in many places, this could be a bit tedious. NOTE TO SELF: For future reference, qq//, qr//, and qw// all had different results (shouldn't be too surprising). The qw// and the q// had the same result. Thank you for your suggestions. Blessings, ~Polyglot~	[reply]
Re^7: Repeated code blocks in long and hairy regex by Corion (Patriarch) on Nov 05, 2023 at 14:26 UTC
... `q//` and `qr//` do different things. You might want to read perlop on what they do, especially on qr and q.	[reply] [d/l] [select]