public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug preprocessor/47823] New: #pragma once not documented
@ 2011-02-20 15:20 olafvdspek at gmail dot com
  2011-02-20 20:42 ` [Bug preprocessor/47823] " pinskia at gcc dot gnu.org
  2012-01-28 19:16 ` [Bug preprocessor/47823] #pragma once is documented in a weird spot pinskia at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: olafvdspek at gmail dot com @ 2011-02-20 15:20 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47823

           Summary: #pragma once not documented
           Product: gcc
           Version: 4.5.2
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: preprocessor
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: olafvdspek@gmail.com


#pragma once appears to be undocumented

http://gcc.gnu.org/onlinedocs/gcc-4.5.2/gcc/Pragmas.html


^ permalink raw reply	[flat|nested] 3+ messages in thread
* [Bug preprocessor/47823] #pragma once not documented
  2011-02-20 15:20 [Bug preprocessor/47823] New: #pragma once not documented olafvdspek at gmail dot com
@ 2011-02-20 20:42 ` pinskia at gcc dot gnu.org
  2012-01-28 19:16 ` [Bug preprocessor/47823] #pragma once is documented in a weird spot pinskia at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2011-02-20 20:42 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47823

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-02-20 20:40:03 UTC ---
At one point it was documented in the C preprocessor manual but it is no longer
documented there.


^ permalink raw reply	[flat|nested] 3+ messages in thread
* [Bug preprocessor/47823] #pragma once is documented in a weird spot
  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
  1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2012-01-28 19:16 UTC (permalink / raw)
  To: gcc-bugs

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.


^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-01-28 19:01 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 ` [Bug preprocessor/47823] #pragma once is documented in a weird spot pinskia at gcc dot gnu.org

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).