unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@twinsun.com>
Cc: rms@gnu.org, sds@gnu.org, emacs-devel@gnu.org
Subject: Re: regex.c: emacs & glibc (and xemacs, and grep and ...)
Date: Mon, 8 Apr 2002 12:22:19 -0700 (PDT)	[thread overview]
Message-ID: <200204081922.g38JMJ015422@shade.twinsun.com> (raw)
In-Reply-To: <200204081626.g38GQfa10456@rum.cs.yale.edu> (monnier+gnu/emacs@rum.cs.yale.edu)

> From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
> Date: Mon, 08 Apr 2002 12:26:41 -0400
> 
> > Would you like to merge some of these versions of regex?
> 
> I'll try and check out GNU grep.

Thanks.  Could you please look at the latest CVS versions:

http://savannah.gnu.org/cgi-bin/viewcvs/grep/grep/lib/regex.c
http://savannah.gnu.org/cgi-bin/viewcvs/grep/grep/lib/regex.h
http://savannah.gnu.org/cgi-bin/viewcvs/grep/grep/lib/posix/regex.h


Please also look at the latest sources in fileutils.  This integrates
all the changes that I know of that occur in textutils, shellutils,
and diffutils.  It is quite close to what was in glibc before the
recent major change to glibc.

ftp://alpha.gnu.org/gnu/fetish/fileutils-4.1.8.tar.gz


libiberty has a copy of regex.c that renames all external
routines with an "x" prefix so they do not collide with the native
regex routines or with other components regex routines.  This sounds
like useful functionality, though I think it should be enabled only if
the user defines a configuration macro.  libiberty may have other
changes; I don't know.

I don't know why the GCC and GDB versions of libiberty regex differ so
greatly.  It appears to me that the GDB versions are newer, but I
suppose there could be useful changes in the GCC version too.

http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/libiberty/regex.c?cvsroot=src
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/include/xregex.h?cvsroot=src
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/include/xregex2.h?cvsroot=src

http://subversions.gnu.org/cgi-bin/viewcvs/gcc/gcc/include/xregex.h
http://subversions.gnu.org/cgi-bin/viewcvs/gcc/gcc/include/xregex2.h
http://subversions.gnu.org/cgi-bin/viewcvs/gcc/gcc/libiberty/regex.c


There are probably other versions of regex.c floating around, but I
think these are the major ones outside Emacs and glibc 2.2.

  reply	other threads:[~2002-04-08 19:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-04 18:55 regex.c: emacs & glibc (and xemacs, and grep and ...) Sam Steingold
2002-04-04 19:24 ` Stefan Monnier
2002-04-05  1:25   ` Paul Eggert
2002-04-05  2:47     ` Miles Bader
2002-04-05 14:48     ` Stefan Monnier
2002-04-05 23:41       ` Richard Stallman
2002-04-08 16:26         ` Stefan Monnier
2002-04-08 19:22           ` Paul Eggert [this message]
2002-04-10 14:23           ` Richard Stallman
2002-04-05 19:05 ` Richard Stallman
2002-04-05 20:27   ` Sam Steingold
2002-04-06 17:32     ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200204081922.g38JMJ015422@shade.twinsun.com \
    --to=eggert@twinsun.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=sds@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).