Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Aug 2002 14:10:03 -0700 (PDT)
From:      Giorgos Keramidas <keramida@FreeBSD.org>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: bin/41159: new sed -c option to allow ; as a separator for b, t and : functions
Message-ID:  <200208202110.g7KLA3cO064035@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/41159; it has been noted by GNATS.

From: Giorgos Keramidas <keramida@FreeBSD.org>
To: Cyrille Lefevre <cyrille.lefevre@laposte.net>
Cc: bug-followup@FreeBSD.org, "Tim J. Robbins" <tjr@FreeBSD.org>
Subject: Re: bin/41159: new sed -c option to allow ; as a separator for b, t and : functions
Date: Wed, 21 Aug 2002 00:04:10 +0300

 Adding to audit trail:
 :
 : Message-Id: <20020801122653.A4231@dilbert.robbins.dropbear.id.au>
 : Date: Thu, 1 Aug 2002 12:26:53 +1000
 : From: Tim Robbins <tjr@FreeBSD.ORG>
 : Subject: Re: new sed -c option to allow ; as a separator for b, t and : functions
 :
 : On Tue, Jul 30, 2002 at 02:40:33PM +0200, Cyrille Lefevre wrote:
 : > 	the current sed implementation can't handle the ; separator for
 : > 	b, t and : functions. this patch set add a new -c (compat) option
 : > 	to allow sed to parse such constructions. maybe -C is better then -c ?
 :
 : If I understand SUSv3 correctly, file names or label names can contain
 : semicolons:
 :
 : 32406	Command verbs other than {, a, b, c, i, r, t, w, :, and # can be
 : 	followed by a semicolon, optional
 : 32407	<blank>s, and another command verb. However, when the s command verb
 : 	is used with the w
 : 32408	flag, following it with another command in this manner produces
 : 	undefined results.
 :
 : GNU sed, which by default accepts semicolons after (at least) the : and t
 : commands does not strictly conform. I'd rather that our sed was by default
 : as close as possible to what the standard requires, so we probably do need
 : a command line option like you suggested.
 :
 : I think -g would be a better choice (similar to m4's -g option) to
 : emphasise the fact that accepting semicolons after these commands is a GNU
 : extension, and possibly adding more GNU compatibility features if
 : they're needed/useful. BSD, 7th Edition and System V all behave the same
 : way, and treat semicolons as part of the label/filename.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200208202110.g7KLA3cO064035>