From: Fergus Henderson <fjh@cs.mu.oz.au>
To: Sam TH <sam@uchicago.edu>, gcc@gcc.gnu.org
Subject: Re: standards for include guards?
Date: Thu, 17 May 2001 08:45:00 -0000 [thread overview]
Message-ID: <20010518014526.A21410@hg.cs.mu.oz.au> (raw)
In-Reply-To: <20010517095918.A18396@uchicago.edu>
On 17-May-2001, Sam TH <sam@uchicago.edu> wrote:
> Without getting into a discussion on the merits of include guards in
> GCC, is there some standard for naming such guards?
This was discussed on gcc-patches a month or so ago, IIRC.
Unfortunately I wasn't able to find it via the search page.
> With the help of
> grep, I have found:
>
> _FILENAME_EXT
> GCC_FILENAME_EXT
> __GCC_FILENAME_EXT__
> _GCC_FILENAME_EXT
> __FILENAME_EXT__
> __filename_ext
> FILENAME_EXT_INCLUDED
> FILENAME_EXT
> _FILENAME_EXT_
> JV_FILENAME_EXT (in java/)
> _DIR_FILENAME_EXT
> _H_f_filename (in f/)
Names starting with `__' or `_[A-Z]' are reserved for use by the C
implementation. Standard library header files, and files which
are included in standard library header files, should use such names.
Other header files which are merely used in gcc (e.g. tree.h) should not.
I *think* the convention agreed on earlier was GCC_FILENAME_EXT.
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
| of excellence is a lethal habit"
WWW: < http://www.cs.mu.oz.au/~fjh > | -- the last words of T. S. Garp.
next prev parent reply other threads:[~2001-05-17 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-17 7:43 Sam TH
2001-05-17 8:45 ` Fergus Henderson [this message]
2001-05-17 9:26 ` Mark Mitchell
2001-05-17 11:27 ` Sam TH
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=20010518014526.A21410@hg.cs.mu.oz.au \
--to=fjh@cs.mu.oz.au \
--cc=gcc@gcc.gnu.org \
--cc=sam@uchicago.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).