Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Hilfinger <hilfingr@gnat.com>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Turn on initial Ada support in GDB
Date: Wed, 29 Sep 2004 08:39:00 -0000	[thread overview]
Message-ID: <20040929083913.2DCEDF2D1B@nile.gnat.com> (raw)
In-Reply-To: <4159A662.2090407@gnu.org> (message from Andrew Cagney on Tue, 28 Sep 2004 13:58:58 -0400)


> >         * Makefile.in (ada_lex_c): Define
> > 	(HFILES_NO_SRCDIR): Add ada-lang.h.
> 
> Can these two lines be put on hold for a moment, there's a symtab change 
> that should be run past the symtab reviewer.
> 
> > 	(COMMON_OBS): Add ada-lang.o, ada-typeprint.o, ada-valprint.o.
> > 	(YYOBJ): Add ada-exp.o.
> 
> otherwize all the Makefile stuff  can go in.
> 
> > 	(rule .l.c): Generalize to not mention ada.
> > 	(ada-lex.o): Remove (ada-lex.c is included by ada-exp.y).
> 
> ... dig dig, ah, bleaugh :-)  Leave this for the moment -> I'll tweak 
> gdb_makefile.sh to better handle this.  Just wonder if the above should 
> be changed from .l.c to .l.h. (but which ever)?

As for .h vs. .c here: I dunno.  I've always thought of .h as meaning
"header" rather than "included".  Besides, if we think of .l.c as a
general 'lex' rule, lex-generated files can just as easily be standalone
as not.

So this is all approved save the HFILES_NO_SRCDIR thing?  I see you 
put in ada_lex_c already.

> > 	* gdbtypes.h (TYPE_FLAG_FIXED_INSTANCE): Define.
> 
> It isn't used.

It's used in several places in ada-lang.c (but not in this patch; it's already
in ada-lang.c, and this patch is needed to make it work).

> > doc ChangeLog:
> > 
> > 2004-09-22  Paul N. Hilfinger  <hilfinger@gnat.com>
> > 
> > 	* gdb.texinfo (Filenames): Add Ada suffixes.
> > 	(Ada) New section.
> 
> For Eli, suggest posting it separatly.

I see that Eli already responded, and I will make the requested changes
before committing.  

OK.  So where does this leave us?  Does all of this amount to a "go"?

Paul


  reply	other threads:[~2004-09-29  8:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-27 10:33 Paul Hilfinger
2004-09-28 17:59 ` Andrew Cagney
2004-09-29  8:39   ` Paul Hilfinger [this message]
     [not found]   ` <20040930073351.6BE79F2BA6@nile.gnat.com>
     [not found]     ` <415CADC5.6050205@gnu.org>
2004-10-01 10:41       ` Paul Hilfinger
     [not found]       ` <20041001102419.78F74F2D17@nile.gnat.com>
     [not found]         ` <415D6817.50005@gnu.org>
2004-10-01 18:25           ` Paul Hilfinger
2004-10-01 20:07             ` Andrew Cagney
2004-09-28 20:14 ` Eli Zaretskii
2004-09-28 20:41   ` Joel Brobecker
2004-09-30 12:56     ` Eli Zaretskii
2004-09-29  8:43   ` Paul Hilfinger

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=20040929083913.2DCEDF2D1B@nile.gnat.com \
    --to=hilfingr@gnat.com \
    --cc=cagney@gnu.org \
    --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