public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/47823] #pragma once is documented in a weird spot Date: Sat, 28 Jan 2012 19:16:00 -0000 [thread overview] Message-ID: <bug-47823-4-7NLtL3YuZn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47823-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47823 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |documentation Status|UNCONFIRMED |NEW Last reconfirmed| |2012-01-28 Summary|#pragma once not documented |#pragma once is documented | |in a weird spot Ever Confirmed|0 |1 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-01-28 19:01:42 UTC --- Confirmed really it is documented but just under #import documentation. It really should be under its own: Another way to prevent a header file from being included more than once is with the @samp{#pragma once} directive. If @samp{#pragma once} is seen when scanning a header file, that file will never be read again, no matter what. @samp{#pragma once} does not have the problems that @samp{#import} does, but it is not recognized by all preprocessors, so you cannot rely on it in a portable program.
prev parent reply other threads:[~2012-01-28 19:01 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-20 15:20 [Bug preprocessor/47823] New: #pragma once not documented olafvdspek at gmail dot com 2011-02-20 20:42 ` [Bug preprocessor/47823] " pinskia at gcc dot gnu.org 2012-01-28 19:16 ` pinskia at gcc dot gnu.org [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=bug-47823-4-7NLtL3YuZn@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).