Date: Tue, 07 May 2002 21:30:03 -0400 (EDT) From: John Baldwin <jhb@FreeBSD.org> To: "J. Mallett" <jmallett@FreeBSD.ORG> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, Garance A Drosihn <drosih@rpi.edu> Subject: Re: cvs commit: src/usr.bin/sed main.c sed.1 Message-ID: <XFMail.20020507213003.jhb@FreeBSD.org> In-Reply-To: <20020508005957.GA28683@FreeBSD.ORG>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08-May-2002 J. Mallett wrote: > On Tue, May 07, 2002 at 08:25:19PM -0400, Garance A Drosihn wrote: >> At 11:30 PM +0000 5/7/02, J. Mallett wrote: >> >I'd go so far as to say we're implementing a superset of Perl's >> >capabilities in sed(1), and as such, the "old code" provision >> >falls in. After all, if you re-implmeneted a whole utility, you >> >would want compatability. All we want is front-end compatability >> >with Perl. The options. >> >> If a user can not be bothered to use '-I .blah' instead of >> '-i.blah', then they can continue to use perl for all I care. >> We do need to be compatible with other versions of sed, but >> not with completely different commands. A user will only >> use the new -i or -I if they read the man page for sed, and >> if they do that then they don't need the optional-argument >> on -i (because they will know they can use -I). > > I like your logic better than the logic I've been using. > > If one or two more people will agree to this, I'll happily make > the necessary changes. Make it so. /me can't wait for sed -ie 's/suckage/good stuff/g' -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20020507213003.jhb>