From: haahr@mv.us.adobe.com (Paul Haahr)
To: alan@oldp.astro.wisc.edu
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: redirection and built-ins
Date: Sun, 6 Jun 1993 20:32:50 -0400 [thread overview]
Message-ID: <9306070032.AA12043@astro.mv.us.adobe.com> (raw)
> 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
next reply other threads:[~1993-06-07 0:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-06-07 0:32 Paul Haahr [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-06-07 17:10 Alan Watson
1993-06-07 15:24 Paul Haahr
1993-06-07 5:23 Alan Watson
1993-06-05 18:59 Alan Watson
1993-06-05 18:45 Paul Haahr
1993-06-05 18:38 Alan Watson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9306070032.AA12043@astro.mv.us.adobe.com \
--to=haahr@mv.us.adobe.com \
--cc=alan@oldp.astro.wisc.edu \
--cc=rc@hawkwind.utcs.toronto.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).