From owner-freebsd-current@FreeBSD.ORG Wed Jun 18 16:23:21 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33A471065679 for ; Wed, 18 Jun 2008 16:23:21 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id B53708FC1C for ; Wed, 18 Jun 2008 16:23:20 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 5862 invoked by uid 399); 18 Jun 2008 16:23:17 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 18 Jun 2008 16:23:17 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <48593673.8030607@FreeBSD.org> Date: Wed, 18 Jun 2008 09:23:15 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.14 (X11/20080606) MIME-Version: 1.0 To: pfgshield-freebsd@yahoo.com References: <188001.76281.qm@web32705.mail.mud.yahoo.com> In-Reply-To: <188001.76281.qm@web32705.mail.mud.yahoo.com> X-Enigmail-Version: 0.95.6 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Diomidis Spinellis , Gabor Kovesdan , current@FreeBSD.org Subject: Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2008 16:23:21 -0000 pfgshield-freebsd@yahoo.com wrote: > On 2008-06-17, Gabor Kovesdan wrote: >>> egrep: empty (sub)expression >>> >> I've looked at this and I have a patch with a workaround: >> http://kovesdan.org/patches/grep.dougb.diff > > This general behavior should be considered a GNUism, the type of > thing that we want to avoid in scripts. Perhaps, if it's too > common, the workaround should be ifdef'd into a GNU compatible mode > or something. No, "here is a new bsd grep, but change all your scripts that have relied on legitimate behavior of grep in the past" is a non-starter. I haven't checked POSIX to see whether the particular construction I am using fits the spec or not, but I really don't care. We need to be feature-compatible with the GNU versions of these tools, both for legacy scripts and also for those users migrating over from linux. Doug -- This .signature sanitized for your protection