-
Notifications
You must be signed in to change notification settings - Fork 560
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
Regex inconsistency with multiple PRUNE/SKIP/COMMIT #12853
Comments
From ph10@hermes.cam.ac.ukCreated by ph10@hermes.cam.ac.ukI have been testing combinations of (*SKIP), (*PRUNE), etc to determine if /aaaaa(*SKIP)b|a+c/ The first matches "ac" and the second "aaaac", entirely as expected. However, /aaaaa(*COMMIT)(*SKIP)b|a+c/ the first still matches "ac", but the second now gives "no match". In all other Here is some evidence of these effects: $ perl -e 'print (("aaaaaac" =~ /aaaaa(*SKIP)b|a+c/)? "$&\n":"no match\n");' Perl Info
|
From @ikegamiOn Fri, Mar 15, 2013 at 7:18 AM, Philip Hazel <perlbug-followup@perl.org>wrote:
(*COMMIT)'s or (*PRUNE)'s behaviour differs from their documentation. |
The RT System itself - Status changed from 'new' to 'open' |
Migrated from rt.perl.org#117179 (status was 'open')
Searchable as RT117179$
The text was updated successfully, but these errors were encountered: