public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eggert at gnu dot org" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug regex/1281] support 64-bit hosts when regex code when used outside glibc
Date: Thu, 01 Sep 2005 22:19:00 -0000	[thread overview]
Message-ID: <20050901221940.16802.qmail@sourceware.org> (raw)
In-Reply-To: <20050831224259.1281.eggert@gnu.org>


------- Additional Comments From eggert at gnu dot org  2005-09-01 22:19 -------
For internal use (in regex_internal.h), I initially started with the
name re_idx_t as you suggested.  But this caused a lot of code
reindenting, since I had to replace "int" by "re_idx_t" in a lot of
places.  Also, the code got more verbose.  Using "Idx" instead of "re_idx_t"
solved that problem.

However, if the consensus is to call it re_idx_t I'd be happy to
produce a new patch that uses the name.

I should mention that this type name is not visible to the user in the
proposed patch.  I was reluctant to introduce the name re_idx_t into
regex.h, because I thought that the user should see just the new
interface, which uses size_t for sizes and offset.  However, if you'd
prefer to make re_idx_t public I can also do that easily.


-- 


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

------- 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:[~2005-09-01 22:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-31 22:43 [Bug regex/1281] New: " eggert at gnu dot org
2005-08-31 22:43 ` [Bug regex/1281] " eggert at gnu dot org
2005-08-31 23:34 ` eggert at gnu dot org
2005-09-01  6:59 ` eggert at gnu dot org
2005-09-01  7:05 ` bonzini at gnu dot org
2005-09-01 18:32 ` eggert at gnu dot org
2005-09-01 22:09 ` eggert at gnu dot org
2005-09-01 22:19 ` eggert at gnu dot org [this message]
2005-09-01 22:20 ` eggert at gnu dot org
2005-09-06 18:11 ` drepper at redhat dot com
2005-09-06 23:47 ` drepper at redhat dot com
2006-04-19 17:43 ` bruno at clisp dot org
2006-04-25 18:01 ` drepper at redhat dot com
2006-04-25 18:20 ` drepper at redhat dot com
2006-04-25 22:54 ` 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=20050901221940.16802.qmail@sourceware.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs@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).