From: Daniel Barlow <dan@telent.net>
To: linux-kernel@vger.kernel.org
Subject: Re: increase the number of system call parameters
Date: 22 Oct 2001 22:37:46 +0100 [thread overview]
Message-ID: <87zo6j8ifp.fsf@noetbook.telent.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0110221334200.1121-100000@hagbart.nvg.ntnu.no> <k2r8rvvq3s.fsf@zero.aec.at>
In-Reply-To: Andi Kleen's message of "22 Oct 2001 14:03:35 +0200"
Andi Kleen <ak@muc.de> writes:
> A note on design: if you have a function call that needs 12 arguments you
> probably forgot some[1] (in short it is a strong cue for a broken design,
> you should probably split it in smaller calls)
> [1] unknown author
If you have a procedure with 10 parameters, you probably missed some.
-- Alan Perlis, SIGPLAN Notices Vol. 17, No. 9
<URL:http://www-pu.informatik.uni-tuebingen.de/users/klaeren/epigrams.html>
-dan
--
http://ww.telent.net/cliki/ - Link farm for free CL-on-Unix resources
prev parent reply other threads:[~2001-10-22 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-22 11:48 increase the number of system call parameters Roar Thronæs
2001-10-22 11:57 ` Matti Aarnio
2001-10-22 12:03 ` Andi Kleen
2001-10-22 21:37 ` Daniel Barlow [this message]
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=87zo6j8ifp.fsf@noetbook.telent.net \
--to=dan@telent.net \
--cc=linux-kernel@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