Date: Wed, 21 Feb 2001 09:39:13 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: "Daniel C. Sobral" <dcs@newsguy.com> Cc: Akinori MUSHA <knu@iDaemons.org>, current@FreeBSD.ORG Subject: Re: find(1) -regex/-iregex Message-ID: <20010221093913.J6641@fw.wintelcom.net> In-Reply-To: <3A9337E0.A51A3E8B@newsguy.com>; from dcs@newsguy.com on Wed, Feb 21, 2001 at 12:37:04PM %2B0900 References: <8666i588p4.wl@archon.local.idaemons.org> <20010220132426.X6641@fw.wintelcom.net> <3A9337E0.A51A3E8B@newsguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Daniel C. Sobral <dcs@newsguy.com> [010220 19:39] wrote: > Alfred Perlstein wrote: > > > > * Akinori MUSHA <knu@iDaemons.org> [010220 11:19] wrote: > > > Hi, > > > > > > I have implemented -regex and -iregex options for find(1): > > > > > > > Sounds good, just make sure the regex engine matches the one that > > the other find(1)'s use. > > It won't. GNU find certainly uses GNU regexp library, which has lots of > extra stuff. Naturally, our find will be using our library instead. > <shrug> Nothing we can do about it. It is the way of the Gnu to extend > and embrace. Well a subset or superset is fine, as long as it's the same type of regex. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010221093913.J6641>