public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "valery_reznic at yahoo dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/14301] Regular expression wrong match with a number of groups
Date: Wed, 27 Jun 2012 08:16:00 -0000 [thread overview]
Message-ID: <bug-14301-132-t6fzi9BOwL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14301-132@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14301
Valery <valery_reznic at yahoo dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
--- Comment #2 from Valery <valery_reznic at yahoo dot com> 2012-06-27 08:15:30 UTC ---
(In reply to comment #1)
> (4[0-9]{12}) matches 4123456789012.
So what?
Regular expression required leading and trailing space to be present for match.
IMO, result for case 3) are wrong
Also please note, that in case 3 and 4 regular expressions are essentially the
same - only (4[0-9]{15}) and (4[0-9]{12}) that connected with OR swapped.
But results are different.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-06-27 8:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 7:26 [Bug regex/14301] New: " valery_reznic at yahoo dot com
2012-06-27 7:48 ` [Bug regex/14301] " schwab@linux-m68k.org
2012-06-27 8:16 ` valery_reznic at yahoo dot com [this message]
2012-06-27 8:33 ` fweimer at redhat dot com
2012-06-27 8:51 ` valery_reznic at yahoo dot com
2014-06-13 14:58 ` fweimer at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-14301-132-t6fzi9BOwL@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs-regex@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).