From: Andrew Cagney <ac131313@redhat.com>
To: gdb@sources.redhat.com
Subject: int foo (); vs int foo (void);
Date: Tue, 10 Jun 2003 19:06:00 -0000 [thread overview]
Message-ID: <3EE62C3A.5000302@redhat.com> (raw)
Ok, so I knew there was a reason for prefering:
> static void
> foo (void)
> {
> }
over
> static void
> foo ()
> {
> }
other than that `the former is strict ISO C'. -Wmissing-prototypes gets
grumpy if it sees the second form. I'd assume that the corresponding
ARI check was added as a cheap -Wmissing-prototypes check.
enjoy,
Andrew
next reply other threads:[~2003-06-10 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 19:06 Andrew Cagney [this message]
2003-06-10 19:17 ` Doug Evans
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=3EE62C3A.5000302@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
/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).