public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "jakub at redhat dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/281] regex.c doesn't compile on hosts with signed char
Date: Fri, 23 Jul 2004 13:47:00 -0000	[thread overview]
Message-ID: <20040723134756.2342.qmail@sourceware.org> (raw)
In-Reply-To: <20040723105653.281.kasal@ucw.cz>


------- Additional Comments From jakub at redhat dot com  2004-07-23 13:47 -------
What kind of problems?
Most of the arches have signed char.
re_search_internal is certainly not the only place which uses
unsigned RE_TRANSLATE_TYPE.
IMHO RE_TRANSLATE_TYPE should stay char *, it has been that way since the
original GNU regex.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING


http://sources.redhat.com/bugzilla/show_bug.cgi?id=281

------- 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:[~2004-07-23 13:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 10:56 [Bug regex/281] New: " kasal at ucw dot cz
2004-07-23 10:59 ` [Bug regex/281] " kasal at ucw dot cz
2004-07-23 13:47 ` jakub at redhat dot com [this message]
2004-07-23 14:45 ` kasal at ucw dot cz
2004-07-26 11:10 ` kasal at ucw dot cz
2004-09-26 21:31 ` drepper at redhat dot com
2004-09-26 22:57 ` kasal at ucw dot cz
2004-09-26 23:00 ` kasal at ucw dot cz
2005-09-23  6:11 ` 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=20040723134756.2342.qmail@sourceware.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --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).