From: Olaf Titz <olaf@bigred.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Where is it written?
Date: Sun, 12 Nov 2000 16:35:59 +0100 [thread overview]
Message-ID: <E13uzAl-0004hs-00@g212.hadiko.de> (raw)
In-Reply-To: <20001110184031.A2704@munchkin.spectacle-pond.org> <200011110011.eAB0BbF244111@saturn.cs.uml.edu> <20001110192751.A2766@munchkin.spectacle-pond.org> <20001111163204.B6367@inspiron.suse.de> <20001111171749.A32100@wire.cadcamlab.org>
> Well it's safer if you are lazy about prototyping varargs functions.
> But of course by doing that you're treading on thin ice anyway, in
> terms of type promotion and portability. So I guess it's much better
> to say "varargs functions MUST be prototyped" and use the registers.
make -Wmissing-prototypes mandatory :-)
Olaf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-12 16:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 16:37 George Anzinger
2000-11-10 23:40 ` Michael Meissner
2000-11-11 0:11 ` Albert D. Cahalan
2000-11-11 0:27 ` Michael Meissner
2000-11-11 1:10 ` H. Peter Anvin
2000-11-11 1:28 ` Keith Owens
2000-11-11 1:33 ` H. Peter Anvin
2000-11-14 1:33 ` Richard Henderson
2000-11-11 5:17 ` Michael Meissner
2000-11-11 14:51 ` Andrea Arcangeli
2000-11-11 15:32 ` Andrea Arcangeli
2000-11-11 23:17 ` Peter Samuelson
2000-11-11 23:30 ` H. Peter Anvin
2000-11-12 4:54 ` Peter Samuelson
2000-11-12 5:21 ` H. Peter Anvin
2000-11-12 5:36 ` Peter Samuelson
2000-11-12 5:55 ` Keith Owens
2000-11-12 9:35 ` Andi Kleen
2000-11-12 12:23 ` Andrea Arcangeli
2000-11-13 5:28 ` H. Peter Anvin
2000-11-12 15:35 ` Olaf Titz [this message]
2000-11-11 1:06 ` H. Peter Anvin
2000-11-10 23:49 ` H. Peter Anvin
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=E13uzAl-0004hs-00@g212.hadiko.de \
--to=olaf@bigred.inka.de \
--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
all inboxes | Powered by JetHome®