From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18013 invoked by alias); 21 Sep 2010 15:30:37 -0000 Received: (qmail 17803 invoked by uid 48); 21 Sep 2010 15:30:08 -0000 Date: Tue, 21 Sep 2010 15:30:00 -0000 Message-ID: <20100921153008.17801.qmail@sourceware.org> From: "eblake at redhat dot com" To: glibc-bugs-regex@sources.redhat.com In-Reply-To: <20090617154705.10290.jbastian@redhat.com> References: <20090617154705.10290.jbastian@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug regex/10290] using REG_ICASE can break ranges X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-regex-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-regex-owner@sourceware.org X-SW-Source: 2010-09/txt/msg00005.txt.bz2 ------- Additional Comments From eblake at redhat dot com 2010-09-21 15:30 ------- In which locale? In the POSIX locale with an ASCII (or similar) encoding, [C-a] is well defined: $ LC_ALL=C sed -n '/[C-a]/p' /dev/null $ LC_ALL=en_US.UTF-8 sed -n '/[C-a]/p' /dev/null sed: -e expression #1, char 7: Invalid range end And since range expressions are only well-defined in the POSIX locale, the point still remains that the case-insensitive flag is messing things up: $ LC_ALL=C sed -n '/[C-a]/I p' /dev/null sed: -e expression #1, char 9: Invalid range end Also, the resolution of this bug should consider http://sources.redhat.com/bugzilla/show_bug.cgi?id=12045, which is unrelated to the REG_ICASE flag. -- http://sourceware.org/bugzilla/show_bug.cgi?id=10290 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.