-
Notifications
You must be signed in to change notification settings - Fork 561
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
regcomp warning gives wrong position of problem #14065
Comments
From @khwilliamsonThis is a bug report for perl from khw@khw.(none), The only warning raised by study_chunk in regcomp.c always says the The reason is that the message uses the parse position pointer The "solution" that occurs to me is simply to not bother to output a Flags: Site configuration information for perl 5.21.4: Configured by khw at Mon Sep 1 11:29:12 MDT 2014. Summary of my perl5 (revision 5 version 21 subversion 4) configuration: Locally applied patches: @INC for perl 5.21.4: Environment for perl 5.21.4: PATH=/home/khw/bin:/home/khw/perl5/perlbrew/bin:/home/khw/print/bin:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/usr/games:/usr/local/games:/home/khw/iands/www:/home/khw/cxoffice/bin |
From @cpansproutOn Mon Sep 01 15:24:36 2014, public@khwilliamson.com wrote:
Confirmed: $ ./perl -Ilib -we '/(a|b)(?=a){3}aaaaaaaaaaaaaa/ if 0'
I suggest you cite the source of the regexp, though, but without the HERE marker: Quantifier unexpected on zero-length expression in regex m/(a|b)(?=a){3}aaaaaaaaaaaaaa/ at -e line 1. Or, we could have a bit of fun: Quantifier unexpected on zero-length expression in regex; not marked by <-- HERE in m/(a|b)(?=a){3}aaaaaaaaaaaaaa/ at -e line 1. :-) -- Father Chrysostomos |
The RT System itself - Status changed from 'new' to 'open' |
From @khwilliamsonOn 09/01/2014 05:06 PM, Father Chrysostomos via RT wrote:
It would have to be Quantifier unexpected on zero-length expression in regex; not |
From @cpansproutOn Mon Sep 01 16:06:54 2014, I wrote:
Done in e1729dc. -- Father Chrysostomos |
@cpansprout - Status changed from 'open' to 'pending release' |
From @khwilliamsonThanks for submitting this ticket The issue should be resolved with the release today of Perl v5.22. If you find that the problem persists, feel free to reopen this ticket -- |
@khwilliamson - Status changed from 'pending release' to 'resolved' |
Migrated from rt.perl.org#122680 (status was 'resolved')
Searchable as RT122680$
The text was updated successfully, but these errors were encountered: