Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!quanta.eng.ohio-state.edu!icarus!kaul From: kaul@icarus.eng.ohio-state.edu (Rich Kaul) Newsgroups: comp.lang.perl Subject: Re: Needed: a pointer for a perl compare script (long, sorry..) Message-ID: Date: 7 Dec 90 17:06:53 GMT References: <1990Dec04.230436.8432@chinet.chi.il.us> <1990Dec5.060300.21410@midway.uchicago.edu> <275E7B47.2EB9@tct.uucp> <1990Dec7.083412.8426@midway.uchicago.edu> Sender: news@quanta.eng.ohio-state.edu Organization: Ohio State University Electrical Engineering Lines: 18 Nntp-Posting-Host: icarus In-reply-to: goer@quads.uchicago.edu's message of 7 Dec 90 08:34:12 GMT Originator: kaul@icarus.eng.ohio-state.edu In article <1990Dec7.083412.8426@midway.uchicago.edu> goer@quads.uchicago.edu (Richard L. Goerwitz) writes: In the case mentioned, I didn't see how perl offered distinct advantages over nawk. Nawk has most of the traits mentioned above, and is much more widely available. I would argue that nawk is not nearly as available as perl. There are quite a few installed machines in which the old awk is all that is available. Even today nawk is not nearly as common as most awk users would like, since few manufacturers ship it -- if you depend on nawk, it's best to carry a copy of gawk with you. If you have a carry a copy of the sources to your tools with you, I'd take perl over awk most any time. Perl has all the options you can ever use and then some ;-). -rich -- Rich Kaul | It wouldn't be research if we kaul@icarus.eng.ohio-state.edu | knew what we were doing.