From: "David O'Brien" <obrien@FreeBSD.org>
To: DJ Delorie <dj@redhat.com>
Cc: jjohnstn@redhat.com, gcc-patches@gcc.gnu.org,
binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: libibery regex
Date: Tue, 10 Jul 2001 21:35:00 -0000 [thread overview]
Message-ID: <20010710213513.A3359@dragon.nuxi.com> (raw)
In-Reply-To: <200107110022.UAA30714@greed.delorie.com>
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)
next prev parent reply other threads:[~2001-07-10 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` DJ Delorie
2001-07-10 21:35 ` David O'Brien [this message]
2001-07-11 8:35 ` DJ Delorie
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=20010710213513.A3359@dragon.nuxi.com \
--to=obrien@freebsd.org \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jjohnstn@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