From owner-freebsd-standards@FreeBSD.ORG Wed Jun 4 09:08:15 2003 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9129637B401; Wed, 4 Jun 2003 09:08:15 -0700 (PDT) Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5B6543F75; Wed, 4 Jun 2003 09:08:13 -0700 (PDT) (envelope-from brandt@fokus.fraunhofer.de) Received: from beagle (beagle [193.175.132.100])h54G86v08066; Wed, 4 Jun 2003 18:08:07 +0200 (MEST) Date: Wed, 4 Jun 2003 18:08:06 +0200 (CEST) From: Harti Brandt To: Tony Finch In-Reply-To: <20030604155534.GQ18938@chiark.greenend.org.uk> Message-ID: <20030604180358.J614@beagle.fokus.fraunhofer.de> References: <20030603144225.GH18938@chiark.greenend.org.uk> <20030603211357.B70533@espresso.bsdmike.org> <20030604104636.A88028@FreeBSD.org> <20030604155534.GQ18938@chiark.greenend.org.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-standards@freebsd.org cc: tjr@freebsd.org Subject: Re: [PATCH] for review Re: Sed substitution bugs X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2003 16:08:15 -0000 On Wed, 4 Jun 2003, Tony Finch wrote: TF>On Wed, Jun 04, 2003 at 10:46:36AM -0500, Juli Mallett wrote: TF>> TF>> We seem to bounce back and forth on what exactly counts as passing TF>> that test.. Tell ya what, run it against SysV or GNU sed, and patch TF>> using the diffs. TF> TF>Solaris: TF>$ echo -n foo | sed y/o/O/ TF>sed: Missing newline at end of file standard input. TF>fOO TF>$ TF> TF>GNU: TF>$ echo -n foo | sed y/o/O/ TF>fOO$ TF> TF>GNU is clearly the right implementation, and it's what the regression TF>test says sed should do. I think sed should be fixed. (I can't do it TF>right now because I'm going climbing.) Either way is correct since, according to posix, sed works only on text files and a file containing the three characters 'f' 'o' 'o' is not a text file. That said, I think, the GNU variant is the more sane 'unspecified' behaviour. harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fraunhofer.de, harti@freebsd.org