public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "jbastian at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/10290] New: using REG_ICASE can break ranges Date: Wed, 17 Jun 2009 15:47:00 -0000 [thread overview] Message-ID: <20090617154705.10290.jbastian@redhat.com> (raw) Using a regular expression range like [C-a] works fine if compiled with regcomp() with just the REG_EXTENDED flag, but if the REG_ICASE flag is added too, regcomp() returns an error "Invalid range end". Testing other ranges with REG_ICASE reveals: [A-Z^-z] is invalid: Invalid range end (11) [A-Z^_`a-z] is ok [C-a] is invalid: Invalid range end (11) [C-f] is ok [_-a] is invalid: Invalid range end (11) [<-a] is ok [z-{] is ok It appears that regcomp() is capitalizing the range if the REG_ICASE flag is used, thus [C-a] becomes [C-A] and since A comes before C, the range is invalid. Likewise, in locales that match ASCII, ^ becomes before z, but after Z, so [A-Z^-z] becomes invalid, and _ comes after A but before a, so [_-a] becomes invalid. If this is not considered a bug, then at the very least, the regex(3) man page should note the side-effects of using REG_ICASE. -- Summary: using REG_ICASE can break ranges Product: glibc Version: 2.9 Status: NEW Severity: normal Priority: P2 Component: regex AssignedTo: drepper at redhat dot com ReportedBy: jbastian at redhat dot com CC: glibc-bugs-regex at sources dot redhat dot com,glibc- bugs at sources dot redhat dot com 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.
next reply other threads:[~2009-06-17 15:47 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-17 15:47 jbastian at redhat dot com [this message] 2009-06-17 15:48 ` [Bug regex/10290] " jbastian at redhat dot com 2010-09-21 15:11 ` bonzini at gnu dot org 2010-09-21 15:30 ` eblake at redhat dot com 2010-09-21 15:58 ` bonzini at gnu dot org
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=20090617154705.10290.jbastian@redhat.com \ --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: linkBe 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).