From: Christoph Hellwig <hch@infradead.org>
To: Simon Que <sque@chromium.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Should new code have forward declarations of static functions or not?
Date: Fri, 18 May 2018 10:06:05 -0700 [thread overview]
Message-ID: <20180518170605.GA22641@infradead.org> (raw)
In-Reply-To: <CANV8Hs3Rc1q_Qcp05jGfuVwqTFg0c9UhNebk24UYGkkGiHpPRA@mail.gmail.com>
On Fri, May 18, 2018 at 12:44:31PM -0400, Simon Que wrote:
> Is it preferred to have forward declarations of static funcs, or to omit
> them altogether?
There are cases where you need them. But in general if you do not
absolutely need them try to avoid them.
prev parent reply other threads:[~2018-05-18 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 16:44 Simon Que
2018-05-18 17:06 ` Christoph Hellwig [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=20180518170605.GA22641@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sque@chromium.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
Powered by JetHome