public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/1149] character class with range doesn't match half-width kana in SJIS locale
Date: Wed, 26 Apr 2006 07:04:00 -0000	[thread overview]
Message-ID: <20060426070409.16787.qmail@sourceware.org> (raw)
In-Reply-To: <20050802043748.1149.kimura.koichi@canon.co.jp>


------- Additional Comments From bonzini at gnu dot org  2006-04-26 07:04 -------
So you WONTFIX a bug just because the patch sent is not for glibc?  Either the
bug is invalid, and you mark it as INVALID; or you just ignore the patch.  But
not WONTFIX.

The patch is not ok because it slows down unnecessarily the function, and regex
is already slow enough.  We probably should cache the results of btowc (at least
for the non _LIBC case).

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |


http://sourceware.org/bugzilla/show_bug.cgi?id=1149

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2006-04-26  7:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02  4:37 [Bug regex/1149] New: " kimura dot koichi at canon dot co dot jp
2005-09-27 20:05 ` [Bug regex/1149] " drepper at redhat dot com
2006-01-27  6:00 ` kimura dot koichi at canon dot co dot jp
2006-02-01  4:48 ` kimura dot koichi at canon dot co dot jp
2006-04-25 18:12 ` drepper at redhat dot com
2006-04-26  7:04 ` bonzini at gnu dot org [this message]
2006-05-02 22:33 ` drepper 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=20060426070409.16787.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).