From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail-relay-2.mv.us.adobe.com ([130.248.1.2]) by hawkwind.utcs.toronto.edu with SMTP id <2726>; Sun, 6 Jun 1993 20:32:24 -0400
Received: by mail-relay-2.mv.us.adobe.com; id AA06856; Sun, 6 Jun 93 17:31:49 -0700
Received: by astro.mv.us.adobe.com; id AA12043; Sun, 6 Jun 93 17:32:50 -0700
Date:	Sun, 6 Jun 1993 20:32:50 -0400
From:	haahr@mv.us.adobe.com (Paul Haahr)
Message-Id: <9306070032.AA12043@astro.mv.us.adobe.com>
To:	alan@oldp.astro.wisc.edu
Subject: Re: redirection and built-ins
Cc:	rc@hawkwind.utcs.toronto.edu

> I suspect that the traditional implementation stems from the lack of
> redirection on built-ins in the orginal shell, but I could be wrong.

i don't think so.  it's the clearest and simplest implementation, and
has completely obvious semantics.

``echo ... | read foo'' is not the appropriate construct in rc or es.
the *right* way to that in one of these shells is

	foo = `{ echo ... }

or

	foo = `` () { echo ... | { read foo | echo -n $foo } }

if you really want read semantics.

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?

paul