From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from relay2.UU.NET ([137.39.1.7]) by hawkwind.utcs.toronto.edu with SMTP id <2776>; Thu, 5 Nov 1992 20:43:08 -0500
Received: from uunet.uu.net (via LOCALHOST.UU.NET) by relay2.UU.NET with SMTP 
	(5.61/UUNET-internet-primary) id AA15084; Thu, 5 Nov 92 20:43:05 -0500
Received: from srg.UUCP by uunet.uu.net with UUCP/RMAIL
	(queueing-rmail) id 203829.28455; Thu, 5 Nov 1992 20:38:29 EST
Received: from ceres.srg.af.mil by srg.srg.af.mil
	id aa29894; Thu, 5 Nov 92 20:22:07 EST
From:	culliton@srg.srg.af.mil (Tom Culliton x2278)
X-Mailer: SCO System V Mail (version 3.2)
To:	byron@netapp.com, rc@hawkwind.utcs.toronto.edu
Subject: Re: aha
Date:	Thu, 5 Nov 1992 20:22:28 -0500
Message-Id: <9211052022.aa01582@ceres.srg.af.mil>

br>	I am inclined to make the two the same, if only because
br>	it simplifies the interface. It also means that you
br>	will be able to set $status from within a signal handler
br>	by using "return", for whatever that's worth.

EEK! Asynchronously? Like between "if ( ! command )" and "echo command
failed with status $status"?  Sounds iffy to me.

OBNiggle - The man page says the following about wait:  "If no pid is
specified, rc waits for >>ANY<< child process to exit."  Which would be
OK because you can always say "while (! ~ $#apids 0) wait", but it is
not the way things really work.  The man page should say: "If no pid is
specified, rc waits for all child processes to exit."