From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from postman.osf.org ([130.105.1.152]) by hawkwind.utcs.toronto.edu with SMTP id <2223>; Tue, 21 Sep 1993 11:09:32 -0400
Received: from sulphur.osf.org by postman.osf.org (5.64+/OSF 1.0)
	id AA08143; Tue, 21 Sep 93 11:09:24 -0400
Received: by sulphur.osf.org (1.37.109.4/4.7) id AA12434; Tue, 21 Sep 93 11:09:50 -0400
Date:	Tue, 21 Sep 1993 11:09:50 -0400
From:	rsalz@osf.org
Message-Id: <9309211509.AA12434@sulphur.osf.org>
To:	rc@hawkwind.utcs.toronto.edu
Subject: Re: Thoughts on a builtin read


>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$