From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from groucho.cs.psu.edu ([130.203.2.10]) by archone.tamu.edu with SMTP id <45335>; Thu, 9 Apr 1992 19:36:17 -0500
Received: from localhost by groucho.cs.psu.edu with SMTP id <2538>; Thu, 9 Apr 1992 20:35:47 -0400
To: Byron Rakitzis <byron@archone.tamu.edu>
cc: rc@archone.tamu.edu
Subject: Re: eval vs & 
In-reply-to: Your message of "Thu, 09 Apr 92 20:19:36 EDT."
             <92Apr9.191943cdt.45334@archone.tamu.edu> 
Date: Thu, 9 Apr 1992 19:35:37 -0500
From: schwartz@groucho.cs.psu.edu
Message-Id: <92Apr9.203547edt.2538@groucho.cs.psu.edu>


| re: eval and &. Well, input for eval is rescanned noninteractively,
| so interactive features get lost during an eval. This is perhaps
| bogomorphic. At the same time, however, you don't want rc to print
| prompts while it chugs through an eval.

I suppose.  But it surprised me while using ``--'', just now.

| re: wait(). rc does not trap SIGCLD, so it cannot notify you
| asynchronously of a child's death. This may be another bogomorphism,
| but so far I've been using Occam's razor, i.e., avoiding complexity
| in the design whenever possible.

Actually async notification is not really what I had in mind.  I was
thinking that when rc does happen to wait(), it could collect all the
statuses and put them in $astatus.  The the prompt function could print
them if you wanted them.