Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: richard@tiptree.demon.co.uk
Cc: Michael Elizabeth Chastain <mec@shout.net>,
	gdb-patches@sources.redhat.com, ezannoni@redhat.com,
	msalter@redhat.com, fnasser@redhat.com, fedor@gnu.org
Subject: Re: [RFA] ObjC Testsuite
Date: Tue, 04 Mar 2003 14:54:00 -0000	[thread overview]
Message-ID: <3E64BE1E.90407@redhat.com> (raw)
In-Reply-To: <8273D87E-4E0C-11D7-97B4-00306544502E@tiptree.demon.co.uk>


> I was getting increasingly worried that, while stuff is being reviewed, none
> of it actually seems to be getting into CVS ... even one of the earliest patches
> to simply add the existing objc code into the configure/make process and
> activate it (which I think one reviewer said was a no-brainer or something
> similar) is still outstanding.

Just FYI, enabling the code for the default build is one of the last 
things to happen, not one of the first.

- gdb's language code isn't modula
There isn't a clean way of dropping in new languages (like many things, 
a developer got half way through the process, and then stopped.  It has 
then remained in that state for ~10 years.  A --with-languages=... isn't 
there.

- this specific code came from [very old] a fork.
As such it needs sigificant work before it gets integrated into GDB. 
Adam has been doing a briliant job.  What's in GDB is noticably 
different to what was in Apple's fork.

Andrew



  reply	other threads:[~2003-03-04 14:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03 16:15 Michael Elizabeth Chastain
2003-03-04  4:45 ` Adam Fedor
2003-03-04  6:42 ` richard
2003-03-04 14:54   ` Andrew Cagney [this message]
2003-03-05  6:15     ` richard
  -- strict thread matches above, loose matches on Subject: below --
2003-02-20  2:19 [RFA]: " Adam Fedor
2003-03-03  2:47 ` Elena Zannoni

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=3E64BE1E.90407@redhat.com \
    --to=ac131313@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=fedor@gnu.org \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    --cc=msalter@redhat.com \
    --cc=richard@tiptree.demon.co.uk \
    /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