From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from oldp.astro.wisc.edu ([128.104.39.15]) by hawkwind.utcs.toronto.edu with SMTP id <2735>; Mon, 7 Jun 1993 01:24:00 -0400
Received: by oldp.astro.wisc.edu (5.65/DEC-Ultrix/4.3)
	id AA07327; Mon, 7 Jun 1993 00:23:47 -0500
Message-Id: <9306070523.AA07327@oldp.astro.wisc.edu>
To:	haahr@mv.us.adobe.com (Paul Haahr)
Cc:	rc@hawkwind.utcs.toronto.edu
Subject: Re: redirection and built-ins 
Date:	Mon, 7 Jun 1993 01:23:47 -0400
From:	Alan Watson <alan@oldp.astro.wisc.edu>
X-Mts: smtp

| ``echo ... | read foo'' is not the appropriate construct in rc or es.

Yeah, because it doesn't work; there is nothing intrinsicly
`inappropriate' about it.  I hadn't realised there was a lexicon of
politically correct idioms in rc, but clearly I have been badly
misinformed...

| read hasn't made it to either of these shells yet.  why are we talking
| about modifying fundamental parts of these shells to support inappropriate
| uses of (as-yet) unimplemented operations?

Sorry, I didn't actually mean to imply that read should be a built-in,
and I was actually thinking of a functionally-implemented read.  When
I mentioned rc forking to provide redirection for built-ins, I was
also thinking about functions, but it was sloppy writing on my part.