Date: Tue, 7 May 2002 13:55:41 -0700 From: Alfred Perlstein <bright@mu.org> To: John Baldwin <jhb@FreeBSD.org> Cc: "J. Mallett" <jmallett@FreeBSD.ORG>, Garrett Rooney <rooneg@electricjellyfish.net>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/sed main.c sed.1 Message-ID: <20020507205541.GL36741@elvis.mu.org> In-Reply-To: <XFMail.20020507153353.jhb@FreeBSD.org> References: <20020507191959.GA26441@FreeBSD.ORG> <XFMail.20020507153353.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* John Baldwin <jhb@FreeBSD.org> [020507 12:34] wrote: > > On 07-May-2002 J. Mallett wrote: > > On Tue, May 07, 2002 at 03:06:37PM -0400, John Baldwin wrote: > >> > >> It still would have been a good idea to send out the actual patch for review > >> on a public list. Personally, I won't use sed -i if it insists on leaving > >> backup files around that I have to go the trouble to delete. I might as > >> well > >> just do sed 'foo' < foo > foo.bak. I only use -i when I'm not specifying a > >> backup extension. Those are the only times I use perl in fact, and thus I > >> will probably continue to use perl for such things. > > > > Various points taken. Tell me the preferred way to handle options which may > > or may not take arguments, and I'll give it my best shot. I'd assume it's > > to do something like > > You can look at the perl source to see how they do it. :) Just open and then unlink the source file then recreate it as the output file. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.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?20020507205541.GL36741>