Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Thu, 7 Jun 2001 21:34:23 -0400
Message-Id: <200106080134.VAA06362@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: ian AT zembu DOT com
CC: gcc AT gcc DOT gnu DOT org, gdb AT sources DOT redhat DOT com, binutils AT sources DOT redhat DOT com,
        cygwin AT sources DOT redhat DOT com
In-reply-to: <si1yovn4f7.fsf@daffy.airs.com> (message from Ian Lance Taylor on
	07 Jun 2001 18:31:08 -0700)
Subject: Re: Another RFC: regex in libiberty
References: <200106080127 DOT VAA01308 AT greed DOT delorie DOT com> <si1yovn4f7 DOT fsf AT daffy DOT airs DOT com>


> gdb already ships with gnu-regex.c.  Why not just move that to
> libiberty?

Because gdb, tcl, expect, cygwin, and gcc each have a copy of regex,
and they're all different.  Which to choose?

> I can't see any reason for a BSD-licensed regex in libiberty.
> libiberty already GPL code.

Any regex added to libiberty becomes part of newlib and cygwin as
well, and those projects are sensitive to GPL vs non-GPL licensing
issues.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple