From: "Jan Beulich" <JBeulich@novell.com>
To: <linux-kernel@vger.kernel.org>
Subject: inline (and variants) function modifier
Date: Fri, 19 Nov 2004 14:26:29 +0100 [thread overview]
Message-ID: <s19df451.058@emea1-mh.id2.novell.com> (raw)
May I ask how one is supposed to write a non-static function and let the
compiler decide whether it is worth inlining? Since all of 'inline',
'__inline', and '__inline__' get __attribute__((always_inline))
attached, I can't see how I would currently do this. Wouldn't it make
sense to leave at least one of the three with its original meaning?
Additionally, while on a subject like this, is there a reason
attributes (as the above) are generally specified without leading (and
trailing) double underscores? This way, if I #define a symbol with the
name of an existing (or even future) attribute, things are going to
break, whereas conventions preclude me from #define-ing symbols with
double leading underscores.
Thank you,
Jan
next reply other threads:[~2004-11-19 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 13:26 Jan Beulich [this message]
2004-11-20 10:02 ` Jan Engelhardt
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=s19df451.058@emea1-mh.id2.novell.com \
--to=jbeulich@novell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome