Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!mips!pacbell.com!pacbell!sactoh0!unify!csusac!utgard!chris
From: chris@utgard.uucp (Chris Anderson)
Newsgroups: comp.unix.questions
Subject: Re: perl
Message-ID: <1990Jun14.094405.10380@utgard.uucp>
Date: 14 Jun 90 16:43:56 GMT
References: <18498@well.sf.ca.us>
Distribution: usa
Organization: QMA, Inc., Rancho Cordova, California
Lines: 28
FollowupTo:
ReplyTo: chris@utgard.UUCP (Chris Anderson)

In article <18498@well.sf.ca.us> gregs@well.sf.ca.us (Greg Strockbine) writes:
>I'm just starting to look at perl. Is there a good reason
>to use it instead of sed, awk, etc.?

Absolutely!  It does much more for you than any of the other standard
utilities.  Anything you can do in them, you can do in perl... usually
faster and more portably.  It's regular expression handling is better
than that supplied with egrep or sed, it is much more efficient than
anything that I've used before for text manipulation, and you can use
it with binary files as well.

I use it a lot for systems administration duties, since the scripts 
will run without change on multiple machines (be careful, though,
perl includes functions for dealing with sockets, symbolic links, and
file locking if you compile it on a BSD machine; AT&T doesn't have those
features yet).  But you can test at runtime for missing features, so
you can still write fairly portable scripts using those functions.

Read comp.lang.perl for awhile, and don't be scared off by the syntax.

Chris


-- 
| Chris Anderson  						       |
| QMA, Inc.		        email : {csusac,sactoh0}!utgard!chris  |
|----------------------------------------------------------------------|
| My employer never listens to me, so why should he care what I say?   |