From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devpts_fs.h fails with "error: parameter name omitted"
Date: Tue, 24 Feb 2004 04:31:21 +0000 (UTC) [thread overview]
Message-ID: <c1ek2p$jq5$1@terminus.zytor.com> (raw)
In-Reply-To: 20040224024942.GG1200@cse.unsw.EDU.AU
Followup to: <20040224024942.GG1200@cse.unsw.EDU.AU>
By author: Ian Wienand <ianw@gelato.unsw.edu.au>
In newsgroup: linux.dev.kernel
>
> On Tue, Feb 24, 2004 at 02:24:24AM +0000, viro@parcelfarce.linux.theplanet.co.uk wrote:
> > That part makes sense. Previous one doesn't.
>
> Is that by convention or is leaving out the parameter name in the
> prototype standardised somewhere?
>
It's commonly done to make code less macro-sensitive.
Personally I wish that standard C allowed it for definitions as well, rather than
having to type (void)foo; to keep it from complaining about unused parameters.
-hpa
prev parent reply other threads:[~2004-02-24 4:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 2:16 [PATCH] devpts_fs.h fails with "error: parameter name omitted" Ian Wienand
2004-02-24 2:24 ` viro
2004-02-24 2:49 ` Ian Wienand
2004-02-24 3:00 ` viro
2004-02-24 4:31 ` H. Peter Anvin [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='c1ek2p$jq5$1@terminus.zytor.com' \
--to=hpa@zytor.com \
--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 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.