From: Andreas Schwab <schwab@suse.de>
To: root@chaos.analogic.com
Cc: Lei Yang <leiyang@nec-labs.com>,
Lee Revell <rlrevell@joe-job.com>,
Sam Ravnborg <sam@ravnborg.org>,
Kernel Newbies Mailing List <kernelnewbies@nl.linux.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problems compiling kernel modules
Date: Mon, 23 Aug 2004 17:48:06 +0200 [thread overview]
Message-ID: <jevff9svnt.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0408231018001.7732@chaos> (Richard B. Johnson's message of "Mon, 23 Aug 2004 10:29:20 -0400 (EDT)")
"Richard B. Johnson" <root@chaos.analogic.com> writes:
> A function looks like this:
>
> int present()
> {
>
> }
>
> A prototype for the same function looks like this:
>
> int present(void);
>
> Functions always have "{}". Prototypes never do.
A function definition is also a prototype unless you use oldstyle
definitions.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-08-23 15:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 19:24 Problems compiling kernel modules Lei Yang
2004-08-21 21:44 ` Sam Ravnborg
2004-08-21 19:45 ` Lei Yang
2004-08-21 20:05 ` viro
2004-08-21 20:13 ` Lee Revell
2004-08-21 21:50 ` Sam Ravnborg
2004-08-21 19:55 ` Lei Yang
2004-08-21 20:46 ` Lei Yang
2004-08-21 20:57 ` Lee Revell
2004-08-23 14:10 ` Lei Yang
2004-08-23 14:29 ` Richard B. Johnson
2004-08-23 14:39 ` Lei Yang
2004-08-23 14:52 ` Richard B. Johnson
2004-08-23 15:04 ` Lei Yang
2004-08-23 15:20 ` Richard B. Johnson
2004-08-23 15:25 ` Sam Ravnborg
2004-08-23 15:44 ` Lei Yang
2004-08-23 16:21 ` Alan Cox
2004-08-23 14:52 ` Alan Cox
2004-08-23 15:48 ` Andreas Schwab [this message]
2004-08-21 21:11 ` Alex Goddard
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=jevff9svnt.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=kernelnewbies@nl.linux.org \
--cc=leiyang@nec-labs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=root@chaos.analogic.com \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.