Date: Wed, 20 Dec 2000 00:54:20 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: arch@FreeBSD.ORG Cc: freebsd-arch@FreeBSD.ORG Subject: Re: gensetdefs using sh(1),sed(1),grep(1) and awk(1) Message-ID: <20001220005420.M19572@fw.wintelcom.net> In-Reply-To: <20001220004012.E41741@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Wed, Dec 20, 2000 at 12:40:13AM -0800 References: <3A405A43.5C10697C@cup.hp.com> <20001219233816.H19572@fw.wintelcom.net> <20001220002218.A41741@dragon.nuxi.com> <20001220003159.J19572@fw.wintelcom.net> <20001220004012.E41741@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* David O'Brien <obrien@FreeBSD.ORG> [001220 00:40] wrote: > On Wed, Dec 20, 2000 at 12:31:59AM -0800, Alfred Perlstein wrote: > > Then YOU write it in such a way that it's all of: > > .) readable, > > Sorry, I do read `sh'. I fail to see what is so hard to read in this > script. David, you parse configure scripts as part of your work, you've seen the most evil uses of sh imaginable. The fact that you can read it doesn't make it maintainable. I also fear that it will turn into something like makesyscalls.'sh' (should be .awk at this point, or .gross even) > > .) comes within double the perl version's cpu time. > > Ok, I toss out GNU Awk and import Mawk. David, I don't give a hoot what you do with awk, just write the script, get it over with or stand out of the way. You need to calm down and pick your battles, a perl script is not worthy of this. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001220005420.M19572>