From: Paul Eggert <eggert@cs.ucla.edu>
To: Arnd Bergmann <arnd@arndb.de>, Florian Weimer <fweimer@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"Dmitry V. Levin" <ldv@altlinux.org>,
Albert ARIBAUD <albert.aribaud@3adev.fr>,
GNU C Library <libc-alpha@sourceware.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: extending wait4(2) or waitid(2) linux syscall
Date: Fri, 16 Nov 2018 16:03:00 -0000 [thread overview]
Message-ID: <5a64c828-b62a-acb4-ca0f-7b343cda3e1a@cs.ucla.edu> (raw)
In-Reply-To: <CAK8P3a2kDbzzdHdPNaU9LBdLbdFejLYzx+Ntt4s5F=7u+scHsg@mail.gmail.com>
On 11/16/18 7:17 AM, Arnd Bergmann wrote:
> we'd want something like
>
> int wait9(...)
We're getting uncomfortably close to the Perlis limit.
"If you have a procedure with 10 parameters, you probably missed some."
Perlis AJ. Epigrams on programming. SIGPLAN Notices. 1982:17(9):7-13.
https://dx.doi.org/10.1145/947955.1083808
http://pu.inf.uni-tuebingen.de/users/klaeren/epigrams.html
next prev parent reply other threads:[~2018-11-16 16:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 13:20 Sixth draft of the Y2038 design document Albert ARIBAUD
2017-06-21 10:22 ` Y2038: seventh draft of the design document and 1st WIP branch Albert ARIBAUD
2018-11-15 14:04 ` Sixth draft of the Y2038 design document Dmitry V. Levin
2018-11-15 14:39 ` Arnd Bergmann
2018-11-15 15:30 ` extending wait4(2) or waitid(2) linux syscall Dmitry V. Levin
2018-11-15 15:38 ` hpa
2018-11-16 7:14 ` Arnd Bergmann
2018-11-16 10:27 ` Florian Weimer
2018-11-16 15:17 ` Arnd Bergmann
2018-11-16 16:03 ` Paul Eggert [this message]
2018-11-16 18:46 ` hpa
2018-11-16 18:48 ` hpa
2018-11-16 7:13 ` Arnd Bergmann
2018-11-16 12:42 ` Dave Martin
2018-11-16 13:40 ` Florian Weimer
2018-11-16 14:26 ` Dave Martin
2018-11-17 1:50 ` Arnd Bergmann
2018-11-26 15:18 ` Florian Weimer
2018-11-26 17:15 ` Arnd Bergmann
2018-11-26 17:27 ` Daniel Colascione
2018-11-28 9:31 ` Florian Weimer
2018-11-28 9:37 ` Christian Brauner
2018-11-28 9:41 ` Florian Weimer
2018-11-28 18:50 ` Daniel Colascione
2018-11-15 18:25 ` Sixth draft of the Y2038 design document hpa
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=5a64c828-b62a-acb4-ca0f-7b343cda3e1a@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=albert.aribaud@3adev.fr \
--cc=arnd@arndb.de \
--cc=fweimer@redhat.com \
--cc=hpa@zytor.com \
--cc=ldv@altlinux.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).