Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cica!iuvax!purdue!haven!uvaarpa!mmdf
From: eichin@athena.mit.edu (Mark W. Eichin)
Newsgroups: comp.lang.perl
Subject: internal pipes? chaining functions?
Message-ID: <1990Sep26.011749.2999@uvaarpa.Virginia.EDU>
Date: 26 Sep 90 01:17:49 GMT
Sender: mmdf@uvaarpa.Virginia.EDU (Uvaarpa Mail System)
Reply-To: eichin@athena.mit.edu
Organization: The Internet
Lines: 13

I've got a script which I was able to express conveniently as
	tr \\015 \\012 | 
	sed -e 's/^[/^[F\n' -e 's/\(%CO:.,[0-9]*,[0-9]*%\)/\1\n/' |
	perl mksc.perl

(where mksc is a while(<>) { if(//)..elsif(//)..else.. } script.) I
expect there is a convenient way of expressing the whole thing in
perl, but I'm not quite sure what it is... Essentially, I'd like to
have the nicer features (like <>) in later stages be able to operate
on the result of earlier ones. Is there a "model" that I'm missing
here, or is this just messy? I know I could do this with three perl
processes easily enough. Going from that to one is the important part.
				_Mark_ <eichin@athena.mit.edu>