From: bk@analytikerna.se (Bengt KLEBERG)
To: rc@archone.tamu.edu
Subject: Re: apid as a list
Date: Tue, 20 Aug 1991 02:38:19 -0500 [thread overview]
Message-ID: <9108200738.AA09666@analytikerna.se> (raw)
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
next reply other threads:[~1991-08-20 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-08-20 7:38 Bengt KLEBERG [this message]
-- strict thread matches above, loose matches on Subject: below --
1991-08-19 17:54 Byron Rakitzis
1991-08-19 20:20 ` Boyd Roberts
1991-08-19 20:25 ` Mark-Jason Dominus
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=9108200738.AA09666@analytikerna.se \
--to=bk@analytikerna.se \
--cc=rc@archone.tamu.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).