New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate error for invalid curly quantifier in regex #12539
Comments
From jrw32982@yahoo.comCreated by jrw32982@yahoo.comEnhancement request. Please tighten up the syntax for regexes, perhaps by adding Currently, if the use of a left curly doesn't match a valid quantifier Of course, any such change would not be backwards compatible, so maybe a Thanks! Perl Info
|
From @jkeenanOn Fri Nov 09 09:01:52 2012, jrw32982@yahoo.com wrote:
Disclaimer: I am not a regex-guts expert; just another regex user. That being said, I doubt that the benefit which Perl users might gain
I'll leave it to others to determine whether we would need to create a Regexes are not easy. They do require study and practice. And regex So -1 from me ... but this will inevitably a community discussion. Thank you for posting the RT. Jim Keenan |
The RT System itself - Status changed from 'new' to 'open' |
From @apPlease refer to |
From @jkeenanOn Wed Nov 21 02:00:20 2012, aristotle wrote:
Aristotle, Karl: Can we get an update on the status of this ticket? Thank you very much. |
From @ap* James E Keenan via RT <perlbug-followup@perl.org> [2013-12-14 01:25]:
Purely in terms of bug tracker concerns I *believe* that this ticket is |
From @khwilliamsonOn 12/13/2013 09:37 PM, Aristotle Pagaltzis wrote:
It is not stalled. What happened in 5.18 is that we now have =item Useless use of '\'; doesn't escape metacharacter '%c' (D deprecated) You wrote a regular expression pattern something like m{ \x\{FF\} }x The interior braces, square brackets, and parentheses are treated as m{ \x{FF} }x This message will be in 5.18 and 5.20 so that everyone relying on the Basically, the backslashes don't have any effect currently. This |
From @khwilliamsonThis is actually already fixed according to the OPs wishes. But I'm not going to resolve it until the final step is made, some releases in the future. The use of such a left brace, as in the example in the ticket, now raises a deprecation warning. I'll wait to resolve this until that warning becomes fatal, rather than write a new ticket for that. |
I believe that a warning is now generated for all occurrences where a left brace is taken as a literal when it might not have been meant to be. That means that if it immediately follows a parenthesis, no warning is generated, as it can only ever be a literal there. There is nothing to quantify. Raising the warning for these contexts broke too much code, so we had to back off. |
Migrated from rt.perl.org#115652 (status was 'open')
Searchable as RT115652$
The text was updated successfully, but these errors were encountered: