Date: Wed, 18 Jun 2008 09:23:15 -0700 From: Doug Barton <dougb@FreeBSD.org> To: pfgshield-freebsd@yahoo.com Cc: Diomidis Spinellis <dds@aueb.gr>, Gabor Kovesdan <gabor@FreeBSD.org>, current@FreeBSD.org Subject: Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo] Message-ID: <48593673.8030607@FreeBSD.org> In-Reply-To: <188001.76281.qm@web32705.mail.mud.yahoo.com> References: <188001.76281.qm@web32705.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48593673.8030607>