Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] missing #include in frame.h?
Date: Wed, 09 Apr 2003 20:44:00 -0000	[thread overview]
Message-ID: <ro1d6jvh03n.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20030409203842.GN1170@gnat.com>

On Wed, 9 Apr 2003 16:38:42 -0400, Joel Brobecker <brobecker@gnat.com> said:

> I am trying to see how much effort it needs to be able to build GDB on
> LynxOS 4.0, and found that gcc emits the following warning:

>     frame.h:698: warning: `struct gdbarch' declared inside parameter list
>     frame.h:698: warning: its scope is only this definition or declaration, which is probably not what you want.

> I am not sure whether we want to include gdbarch.h or not. Should we?
> Or maybe we should be including "defs.h". Shall I go ahead and do that
> (add #include "defs.h", and update Makefile.in)?

My impression is that the right thing in these situations is normally
to put an opaque declaration of the struct in question at the top of
the header file:

  struct gdbarch;

That way, header files can be included in any order without forcing
them to include each other.

But shouldn't all .c files inculde defs.h first?  (Indeed, that's what
GDB Internals says.)  Which file were you compiling when you got this
error?  Probably that file should be fixed to include defs.h before
frame.h, instead of changing frame.h.

David Carlton
carlton@math.stanford.edu


  reply	other threads:[~2003-04-09 20:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09 20:38 Joel Brobecker
2003-04-09 20:44 ` David Carlton [this message]
2003-04-09 20:56   ` Joel Brobecker
2003-04-09 21:08     ` David Carlton
2003-04-09 21:22     ` Andrew Cagney
2003-04-09 20:51 ` 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=ro1d6jvh03n.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@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