From: Mark Mitchell <mark@codesourcery.com>
To: sam@uchicago.edu
Cc: gcc@gcc.gnu.org
Subject: Re: standards for include guards?
Date: Thu, 17 May 2001 09:26:00 -0000 [thread overview]
Message-ID: <20010517092433D.mitchell@codesourcery.com> (raw)
In-Reply-To: <20010517095918.A18396@uchicago.edu>
We should use this one:
GCC_FILENAME_EXT
Anything starting with an `_' is invalid for use in user code.
Anything not starting with `GCC' is likely-ish to be used somewhere
else.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2001-05-17 9:26 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
2001-05-17 9:26 ` Mark Mitchell [this message]
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=20010517092433D.mitchell@codesourcery.com \
--to=mark@codesourcery.com \
--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).