Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Elena Zannoni <ezannoni@redhat.com>, Michal Ludvig <mludvig@suse.cz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] dwarf2cfi cleanup + new file
Date: Fri, 17 May 2002 10:51:00 -0000	[thread overview]
Message-ID: <3CE54312.6010807@cygnus.com> (raw)
In-Reply-To: <15589.5531.423925.941457@localhost.redhat.com>


> Almost.  If we decide to introduce a dwarf2read.h file (I think this
> is a good idea) then we should also eliminate the extern's that are in
> symfile.h.  I.e.:
> 
> /* From dwarf2read.c */
> extern int dwarf2_has_info (bfd * abfd);
> extern void dwarf2_build_psymtabs (struct objfile *, int);
> extern void dwarf2_build_frame_info (struct objfile *);
> 
> The dwarf2_build_frame_info should definitely go in dwarf2cfi.h, since
> it's coming from dwarf2cfi.c, not dwarf2read.c.  Then we should add
> the appropriate #include's to all the files that need these functions
> (not too many, luckily) and update the makefile dependencies.
> 
> As far as dwarf2read.h, below:
> 
>  #include "bfd.h"

Already included by "defs.h".

>  #include "objfiles.h"
> 
> Gdb is trying to get away from nested includes. These should go in the 
> files that include dwarf2read.h.

Yes, see:

http://sources.redhat.com/gdb/onlinedocs/gdbint_13.html#SEC111

There can be cases where one header includes another - for a typedef or 
enum.  This fortunatly isn't one of them:

"bfd.h" is already included by "defs.h".
"objfile.h" can be replaced by ``struct objfile;''.

And I've no idea where file_ptr is comming from.  Nope, found it - "bfd.h".

Good move.  Don't forget the makefile :-)

enjoy,
Andrew



  reply	other threads:[~2002-05-17 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-17  6:14 Michal Ludvig
2002-05-17  7:37 ` Elena Zannoni
2002-05-17 10:51   ` Andrew Cagney [this message]
2002-05-17 13:36     ` 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=3CE54312.6010807@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mludvig@suse.cz \
    /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