Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* Re: libibery regex
       [not found]     ` <3B4B4E2F.3DEFD9E7@cygnus.com>
@ 2001-07-10 17:22       ` DJ Delorie
  2001-07-10 21:35         ` David O'Brien
  0 siblings, 1 reply; 3+ messages in thread
From: DJ Delorie @ 2001-07-10 17:22 UTC (permalink / raw)
  To: jjohnstn; +Cc: gcc-patches, binutils, gdb

I committed this, and mirrored it to src as well.  Tested on Linux
(but of course a new file with unique names "shouldn't affect
anything" ;).

Thanks!

To all: If you want GNU regex (from glibc, and I will strive to keep
it in sync), just include "xregex.h" in your source and libiberty will
provide you with it.  No need to do anything special, as xregex
#defines all the usual names (regcmp, etc) to "x" names (xregcmp,
etc).

> 2001-07-10  Jeff Johnston  <jjohnstn@redhat.com>
> 
> 	* Makefile.in: Add support for regex code.
> 	* regex.c: New file.
> 
> The include directory ChangeLog is:
> 
> 2001-07-10  Jeff Johnston  <jjohnstn@redhat.com>
> 
> 	* xregex.h: New file to support libiberty regex.
> 	* xregex2.h: Ditto.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: libibery regex
  2001-07-10 17:22       ` libibery regex DJ Delorie
@ 2001-07-10 21:35         ` David O'Brien
  2001-07-11  8:35           ` DJ Delorie
  0 siblings, 1 reply; 3+ messages in thread
From: David O'Brien @ 2001-07-10 21:35 UTC (permalink / raw)
  To: DJ Delorie; +Cc: jjohnstn, gcc-patches, binutils, gdb

On Tue, Jul 10, 2001 at 08:22:42PM -0400, DJ Delorie wrote:
> To all: If you want GNU regex (from glibc, and I will strive to keep
> it in sync), just include "xregex.h" in your source and libiberty will
> provide you with it.  No need to do anything special, as xregex
> #defines all the usual names (regcmp, etc) to "x" names (xregcmp,
> etc).

I don't quite understand the need of this.  What is wrong with using
native regex libs (if they exist).  This makes it sound like this version
would always be used -- adding to code bloat.

-- 
-- David  (obrien@FreeBSD.org)


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: libibery regex
  2001-07-10 21:35         ` David O'Brien
@ 2001-07-11  8:35           ` DJ Delorie
  0 siblings, 0 replies; 3+ messages in thread
From: DJ Delorie @ 2001-07-11  8:35 UTC (permalink / raw)
  To: obrien; +Cc: jjohnstn, gcc-patches, binutils, gdb

> I don't quite understand the need of this.  What is wrong with using
> native regex libs (if they exist).  This makes it sound like this
> version would always be used -- adding to code bloat.

The problem is that libiberty can't conditionally provide the right
regex header based on what it determines about the host regex.

Programs which use <regex.h> will NOT use libiberty's regex.  Programs
that use "xregex.h" will ALWAYS use libiberty's regex, which is always
the "latest" GNU regex.

If your package can reliably detect if the host regex is acceptable,
then use that conditional to select between regex.h and xregex.h and
you'll get what you want.

However, many projects include a complete local copy of GNU regex and
use that.  This patch at least collects those to one location and
keeps it up to date (there are at least two or three places, I think).
We want to get rid of those local copies.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2001-07-11  8:35 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <200107091924.PAA15845@greed.delorie.com>
     [not found] ` <3B4B2F4C.257185A8@cygnus.com>
     [not found]   ` <200107101645.MAA08773@greed.delorie.com>
     [not found]     ` <3B4B4E2F.3DEFD9E7@cygnus.com>
2001-07-10 17:22       ` libibery regex DJ Delorie
2001-07-10 21:35         ` David O'Brien
2001-07-11  8:35           ` DJ Delorie

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox