Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!psuvax1!rutgers!mcnc!uvaarpa!mmdf
From: eichin@athena.mit.edu (Mark W. Eichin)
Newsgroups: comp.lang.perl
Subject: Re: internal pipes? chaining functions?
Message-ID: <1990Sep27.074114.28684@uvaarpa.Virginia.EDU>
Date: 27 Sep 90 07:41:14 GMT
Sender: mmdf@uvaarpa.Virginia.EDU (Uvaarpa Mail System)
Reply-To: eichin@athena.mit.edu
Organization: The Internet
Lines: 16

I wrote
: 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

Actually, Larry's right, I left out a slash after the first
expression, but I also neglected to clarify something: \n above is a
literal newline, as ^[ is a literal escape.
	The problem I specifically need to address is that both of the
sed expressions insert newlines. With the pipe, perl interprets them
as seperate lines. 
	It occurs to me that I can probably do something like
for (split(/\n/)) around the final perl script to be sure it gets
individual lines. That'll do.
				Thanks...		_Mark_