From: Dave Jones <davej@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Josh Triplett <josh@joshtriplett.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michal Marek <mmarek@suse.cz>, Sam Ravnborg <sam@ravnborg.org>,
Rashika Kheria <rashika.kheria@gmail.com>
Subject: Re: #pragma once?
Date: Mon, 6 Jan 2014 16:50:57 -0500 [thread overview]
Message-ID: <20140106215057.GB25059@redhat.com> (raw)
In-Reply-To: <20140106213349.GF28490@thunk.org>
On Mon, Jan 06, 2014 at 04:33:49PM -0500, Theodore Ts'o wrote:
> On Mon, Jan 06, 2014 at 12:47:07PM -0800, Josh Triplett wrote:
> > Does anyone have any objection to the use of "#pragma once" instead of
> > the usual #ifndef-#define-...-#endif include guard? GCC, LLVM/clang,
> > and the latest Sparse all support either method just fine. (I added
> > support to Sparse myself.) Both have equivalent performance. "#pragma
> > once" is simpler, and avoids the possibility of a typo in the defined
> > guard symbol.
>
> Does anybody know whether other static code analysis tools such as
> Coverity can handle #pragma once?
Coverity should be fine. If it does break, I'm sure they'd fix it.
Dave
next prev parent reply other threads:[~2014-01-06 21:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 20:47 #pragma once? Josh Triplett
2014-01-06 21:00 ` Andrew Morton
2014-01-06 21:09 ` Josh Triplett
2014-01-06 21:33 ` Theodore Ts'o
2014-01-06 21:50 ` Dave Jones [this message]
2014-01-07 5:55 ` Sam Ravnborg
2014-01-07 9:48 ` Geert Uytterhoeven
2014-01-07 10:09 ` Michal Marek
2014-01-07 10:38 ` Josh Triplett
2014-01-07 10:50 ` Josh Triplett
2014-01-12 16:14 ` Patrick Palka
2014-01-13 5:53 ` Josh Triplett
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=20140106215057.GB25059@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=josh@joshtriplett.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rashika.kheria@gmail.com \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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