Re^2: Roughly matching an ipv6 address with sql wildcard

Replies are listed 'Best First'.
Re^3: Roughly matching an ipv6 address with sql wildcard by graff (Chancellor) on Sep 10, 2015 at 02:03 UTC
The extra parens are needed in order for the anchors to do what you want. The OP regex was really saying: "if the string STARTS with an IPv6 string, OR if it ENDS with something that contains one or more IP address characters and/or percent signs". BTW, you might want to include underscore as a possible sql wildcard character, because it is (and can be very useful in certain cases).	[reply]
Re^4: Roughly matching an ipv6 address with sql wildcard by neilwatson (Priest) on Sep 10, 2015 at 12:16 UTC
Does that mean that \A and \Z bind more tightly than \| and if so, where is this precedence listed? Neil Watson watson-wilson.ca	[reply]
Re^5: Roughly matching an ipv6 address with sql wildcard by graff (Chancellor) on Sep 10, 2015 at 14:12 UTC
Everything is explained in the perlre man page. The first subsection under "Regular Expressions" is "Metacharacters", where it should be clear that there is no difference in "precedence" between anchors and the alternation operator (\A and \Z are just variations on ^ and $). In fact, it's not so much a matter of "binding" or "precedence", but rather an issue of "grouping" (via parens, which are also explained in that same section).	[reply]
Re^3: Roughly matching an ipv6 address with sql wildcard by Anonymous Monk on Sep 10, 2015 at 02:12 UTC
You are right on all counts. I do not know why the extra brackets are needed. I must sleep on it. :) qr{\A ipv6 \| alt \Z}imxs Its either begin string with ipv6 or end string with alt other regex tools, ppixregexplain.pl ... Read more... (2 kB) rxrx Read more... (650 Bytes)	[reply] [d/l] [select]