Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@wins.uva.nl>
To: gdb@sources.redhat.com
Subject: GDB's #include file policy revisited
Date: Fri, 07 Sep 2001 04:31:00 -0000	[thread overview]
Message-ID: <200109071131.f87BVlp09896@delius.kettenis.local> (raw)

From the intefnals manual:

      With the exception of the global definitions supplied by `defs.h', a
   header file should explictily include the header declaring any
   `typedefs' et.al. it refers to.

The header `gdbtypes.h' uses `struct block *' in a few function
prototypes, which isn't declared in the file itself.  The rule above
seems to suggest that we should include `symtab.h'.  Alternatively, we
could simply use a forward declaration for `struct block *' in
`gdbtypes.h'.  That would avoid dragging in a lot of unecessary
cruft.  Some of the `tm.h' headers already do something like that, see
for example `config/i386/tm-i386.h'.  Do people agree that this is the
right thing to do?  Should I submit a patch for the internals manual
to turn this into an official policy?

Mark



             reply	other threads:[~2001-09-07  4:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-07  4:31 Mark Kettenis [this message]
2001-09-07 10:16 ` Andrew Cagney

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=200109071131.f87BVlp09896@delius.kettenis.local \
    --to=kettenis@wins.uva.nl \
    --cc=gdb@sources.redhat.com \
    /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