public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: gcc@gcc.gnu.org
Subject: Re: tree.h vs include guard
Date: Thu, 29 Aug 2002 16:48:00 -0000	[thread overview]
Message-ID: <20020829234802.GY31786@codesourcery.com> (raw)
In-Reply-To: <m3wuqef07m.fsf@soliton.integrable-solutions.net>

On Mon, Aug 26, 2002 at 11:17:33AM +0200, Gabriel Dos Reis wrote:
> Zack Weinberg <zack@codesourcery.com> writes:
> 
> | On Wed, Aug 14, 2002 at 02:54:29AM +0200, Gabriel Dos Reis wrote:
> | > 
> | > Hi,
> | > 
> | >   I noticed that tree.h has no guard to prevent multiple-inclusions.
> | > Why so?  FWIW, c-tree.h, c-common.h and cp-tree.h do have such a
> | > thing.
> | 
> | Patches to add multiple include guards to all of GCC's internal
> | headers have been submitted in the past, but never approved and
> | applied, probably because they'd need an OK from someone with global
> | write privileges and all those people were too busy to review the
> | patch.
> | 
> | It was agreed, last time this came up, that in principle they should
> | all have guards.
> 
> Thanks for the reminder.  Do you have references to those patches?
> I realized that we're in stage 3, so maybe those patches are
> inappropriate at this moment; but I think they should be queued for
> after mainline is unfrozen.

http://gcc.gnu.org/ml/gcc-patches/2001-02/msg01342.html and followups.
This is something that could go on the gcc-3_4-basic-improvements-branch,
if we could get review for it.  The patches need updating.

zw

  reply	other threads:[~2002-08-29 16:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-13 17:57 Gabriel Dos Reis
2002-08-13 19:21 ` Devang Patel
2002-08-26  0:18 ` Zack Weinberg
2002-08-26  2:22   ` Gabriel Dos Reis
2002-08-29 16:48     ` Zack Weinberg [this message]
2002-08-29 17:34       ` Richard Henderson
2002-08-13 20:08 Stan Shebs
2002-08-13 20:31 ` Gabriel Dos Reis
2002-08-13 23:29 ` Neil Booth

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=20020829234802.GY31786@codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    /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).