public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "jim at meyering dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/11244] re_compiler_pattern fails to diagnose [b-a] as an invalid range
Date: Wed, 03 Feb 2010 17:47:00 -0000 [thread overview]
Message-ID: <20100203174734.891.qmail@sourceware.org> (raw)
In-Reply-To: <20100203164729.11244.jim@meyering.net>
------- Additional Comments From jim at meyering dot net 2010-02-03 17:47 -------
(In reply to comment #1)
> (RE_SYNTAX_POSIX_EGREP & RE_NO_EMPTY_RANGES) == 0
Thanks.
The real problem is that the non-_LIBC code (which is used in gnulib) performs
the range test regardless of whether RE_NO_EMPTY_RANGES is set. The non-LIBC
function currently lacks access to the "syntax" variable.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11244
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-02-03 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 16:47 [Bug regex/11244] New: " jim at meyering dot net
2010-02-03 17:13 ` [Bug regex/11244] " schwab at linux-m68k dot org
2010-02-03 17:47 ` jim at meyering dot net [this message]
[not found] <bug-11244-132@http.sourceware.org/bugzilla/>
2014-06-30 18:51 ` 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=20100203174734.891.qmail@sourceware.org \
--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).