From: rsalz@osf.org
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: Thoughts on a builtin read
Date: Tue, 21 Sep 1993 11:09:50 -0400 [thread overview]
Message-ID: <9309211509.AA12434@sulphur.osf.org> (raw)
>Well, let me put it this way: I always wanted $status to reflect
>the exit status of the backquote command, not the assignment.
Let me make sure I understand. You want to be able to write this:
x=`read
I understand the consistency argument. Since most uses of read will be
in a "read until EOF loop," however, you would require that other changes
be made to rc. I think this is enough to kill your idea.
Anyhow, let's take a look at your idea. That is,
x=`foobar
should set $status to the exit value of foobar. What should
x=foobar
set $status to? Leave it unchanged? What about
x=*
if the directory is empty? And if it isn't? What about
x=/foo/*
when /foo doesn't exist?
You are making a simple shell very complicated, don't you think?
/r$
next reply other threads:[~1993-09-21 15:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-09-21 15:09 rsalz [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-09-22 17:18 Steve_Kilbane
1993-09-21 17:26 Arnold Robbins
1993-09-21 17:11 rsalz
1993-09-21 16:58 Arnold Robbins
1993-09-21 16:52 gjv%atlas%cesar
1993-09-21 16:36 Byron Rakitzis
1993-09-21 16:50 ` Chris Siebenmann
1993-09-21 15:56 malte
1993-09-21 17:02 ` Chris Siebenmann
1993-09-21 15:54 Tom Culliton x2278
1993-09-21 15:15 Alan Watson
1993-09-21 14:33 malte
1993-09-21 14:20 rsalz
1993-09-21 6:51 malte
1993-09-21 14:19 ` Chris Siebenmann
1993-09-20 22:11 Tom Culliton x2278
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=9309211509.AA12434@sulphur.osf.org \
--to=rsalz@osf.org \
--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).