From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from sunic.sunet.se ([192.36.125.2]) by archone.tamu.edu with SMTP id <22531>; Tue, 20 Aug 1991 03:51:22 -0500
Received: by sunic.sunet.se (5.61+IDA/KTH/LTH/1.199)
	id AAsunic11085; Tue, 20 Aug 91 10:50:30 +0200
Received: by analytikerna.se (4.1/SMI-4.1)
	id AA09666; Tue, 20 Aug 91 09:38:19 +0200
Date: Tue, 20 Aug 1991 02:38:19 -0500
From: bk@analytikerna.se (Bengt KLEBERG)
Message-Id: <9108200738.AA09666@analytikerna.se>
To: rc@archone.tamu.edu
Subject: Re:  apid as a list

Let me quote Byron RAKITZIS:

	It's been suggested that $apid should be a list of all backgrounded jobs,
	and that as soon as rc's wait builtin receives the exit status of an exiting
	child, the appropriate $apid list entry should be removed.

	I have certainly noticed myself writing code like:

	foo &
	apids=$apid
	bar &
	apids=($apid $apids)

	...

	kill $apids

	I will probably implement this in a trial fashion, and ignore it if it is
	too much work, but it doesn't look like it would be too hard. Any comments?

end quote==========================================================================

I would vote for not having it. The code above looks simple enough as
to be possible to use instead. Are there any other advantages, apart
from making this manual concattenating of pids unnecessary?

Bengt