From: Sam TH <sam@uchicago.edu>
To: gcc@gcc.gnu.org
Subject: standards for include guards?
Date: Thu, 17 May 2001 07:43:00 -0000 [thread overview]
Message-ID: <20010517095918.A18396@uchicago.edu> (raw)
Without getting into a discussion on the merits of include guards in
GCC, is there some standard for naming such guards? 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/)
Then, the weird ones:
java/parse.h: JV_LANG_H
gstab.h: __GNU_STAB__
glimits.h: __LIMITS_H_
Maybe something should be picked?
sam th --- sam@uchicago.edu --- http://www.abisource.com/~sam/
OpenPGP Key: CABD33FC --- http://samth.dyndns.org/key
DeCSS: http://samth.dynds.org/decss
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.5 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7A+dGt+kM0Mq9M/wRAt1EAJ4haEtZaamxZYaXlLzHra8iFv/DlgCfacdI
xwj+2EJxzALt1CMInPjQpbM=
=5j+T
-----END PGP SIGNATURE-----
next reply other threads:[~2001-05-17 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-17 7:43 Sam TH [this message]
2001-05-17 8:45 ` Fergus Henderson
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=20010517095918.A18396@uchicago.edu \
--to=sam@uchicago.edu \
--cc=gcc@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: 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).