Re: regex bug in perl 5.8.7

You need a re-entrant regexp engine to do what you tried. I don't think even the latest bleads are. Also, your pattern isn't terribly meaningful. Are you *sure* you meant to use the return value of a boolean regexp as another regexp pattern to compile and apply?

⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊

Comment on Re: regex bug in perl 5.8.7

Replies are listed 'Best First'.
Re^2: regex bug in perl 5.8.7 by imp (Priest) on May 25, 2007 at 23:44 UTC
The pattern isn't meant to be meaningful. The regex I listed was already reduced to the simplest case I could find that still caused a segfault. The original form was much different.	[reply]
Re^3: regex bug in perl 5.8.7 by diotalevi (Canon) on May 26, 2007 at 00:12 UTC
In the future, you might want to use the (?{...}) form instead since that has no implications for compiling and interpolating another regexp. ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊	[reply]
Re^4: regex bug in perl 5.8.7 by imp (Priest) on May 26, 2007 at 04:31 UTC
The regex that originally triggered the segfault was an attempt at a joke that used a modified version of the regex I wrote in this node. The joke was that someone in an irc channel at work said "<3", and someone else asked what the opposite of "<3" was. My response was `qr[(??{/^<3/?qr/\A\z/:qr//;})]` Which is this when written in a legible manner: `my $negative = qr[ (??{ /^<3/ ? qr/\A\z/ : qr//; }) ]x;` [download] Which segfaulted, but only when the text being searched started with '<3'. After a little exploration I found the minimal regex that still segfaulted, and posted about it.	[reply] [d/l] [select]


good chemistry is complicated, and a little bit messy -LW
	PerlMonks