Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!noao!ncar!gatech!psuvax1!news
From: schwartz@groucho.cs.psu.edu (Scott Schwartz)
Newsgroups: comp.os.misc
Subject: Re: Globbing
Message-ID: <1q6Gblxf1@cs.psu.edu>
Date: 3 Apr 91 07:02:13 GMT
References: <=baGj#dc1@cs.psu.edu> <44480@cos.com> <?55G-t_e1@cs.psu.edu>
	<186@blars>
Sender: news@cs.psu.edu (Usenet)
Organization: PSU CS
Lines: 23
In-Reply-To: blarson@blars's message of 3 Apr 91 06:05:08 GMT
Nntp-Posting-Host: groucho.cs.psu.edu


In article <186@blars> blarson@blars writes:

| Scott Schwartz writes:
| >Yes, although I should clarify that Primos' command processor doesn't
| >do redirection itself.
| 
| Untrue, it can redirect input from a file (comi command) and redirect
| output to a file (in adition to or instead of the terminal) (como command).

You are correct about comi, but (at least as of rev20, when I last
used primos) como had the unfortunate property of printing both input
and output, with no way to distinguish them after the fact.  If it
would just print output everything would have been great.  (If there
was a way to do that in rev19 or 20, I wish you'd have let me know in
1985!  :-)

| And didn't like how your own code worked.  Not something to blame on Primos.

I'm not blaming primos, just commenting that iteration had an
particular side effect.  And, as others have said, it points out one
of the things to watch out for if you do implement iteration in a Unix
shell if you want it to interact properly with redirection.