Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Adam Fedor <fedor@doc.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Objective-C language support.
Date: Wed, 18 Sep 2002 11:57:00 -0000	[thread overview]
Message-ID: <3D88CC99.8010803@ges.redhat.com> (raw)
In-Reply-To: <3D88BCD1.5379F383@redhat.com>

> Adam Fedor wrote:
> 
>> 
>> This patch adds Objective-C language support to gdb based upon a patch
>> provided by Apple Computer Inc from their version of gdb. Note that the
>> patch only contains changes to existing files. New files (objc-lang.h,
>> objc-lang.c, objc-exp.y) and a gdb.objc testsuite directory are located at
>> 
>> ftp://ftp.gnustep.org/pub/gnustep/contrib/gdb-objc-patch.tar.gz
>> 
> 
> 
> 
> Oh lord.  I suppose I am the only one here who is 
> even noddingly familiar with Objective C?
> 
> There's a good chance that I wrote some of this code
> anyway, so I'll try to have a look at it.  You know, 
> of course, that we can't just drop something this huge
> into the source tree without some review...
> 
> I'll need the ability to run the tests.  Does GCC already
> have enough objc to compile them?  Will I need any special
> libraries?

For Ada, a different approach has been taken:

- commit the new files (but not changes to old files)
- commit the makefile rules for the new files (but not changes that 
would cause these files to build by default)
- clean the files up so that they meet current coding conventions - 
-Werror, ARI, ... (for Ada the files were all K&R, looking back.)
- slowly contribute/merge the patches to other files
- add the missing makefile bits making it part of GDB

This way, the bulk of the code is in the mainline.  I think it works 
better since:

- people can see the code (there have already been several patches go 
through where the Ada code was ``fixed'' for free, just by virtue of 
being part of the repository).
- while being developed, doesn't break the existing builds

With this, the worst that can happen is the code never gets enabled.

The other thing is that, very like when someone adds new a architecture, 
other than the contributor, no one immediatly cares if it doesn't work 
quite right.  Just as long as it hasn't actually broken other parts of 
GDB and hasn't hasn't done anything really really nasty at the 
implementation level (ari and -Werror cover most of that).

enjoy,
Andrew



  parent reply	other threads:[~2002-09-18 18:57 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18  8:24 Adam Fedor
2002-09-18 10:50 ` Michael Snyder
2002-09-18 11:57   ` Michael Snyder
2002-09-18 11:57   ` Andrew Cagney [this message]
2002-09-18 12:04     ` Michael Snyder
2002-09-18 12:14       ` Andrew Cagney
2002-09-18 12:17         ` Michael Snyder
2002-09-18 13:51           ` Adam Fedor
2002-09-18 15:00             ` Michael Snyder
2002-09-18 15:19               ` Adam Fedor
2002-09-18 15:25               ` Andrew Cagney
2002-09-18 11:59   ` Daniel Berlin
2002-09-18 13:31   ` Adam Fedor
2002-09-18 14:03 ` Andrew Cagney
2002-10-08 16:36 ` Michael Snyder
2002-10-11 19:29   ` Adam Fedor
2002-10-08 16:42 ` Michael Snyder
2002-10-11 19:44   ` Adam Fedor
2002-10-21 15:18   ` Andrew Cagney
2002-10-21 15:27     ` Michael Snyder
2002-10-08 16:45 ` Michael Snyder
2002-10-11 19:39   ` Adam Fedor
2002-10-08 16:51 ` Michael Snyder
2002-10-14 13:06   ` Jim Blandy
2002-10-21 15:28     ` Andrew Cagney
2002-10-22 17:04       ` Michael Snyder
2002-10-22 18:42         ` Elena Zannoni
2002-10-08 16:58 ` Michael Snyder
2002-10-14 19:18   ` Adam Fedor
2002-10-21 15:31   ` Andrew Cagney
2002-10-08 17:01 ` Michael Snyder
2002-10-14 13:08   ` Jim Blandy
2002-10-18 10:06     ` Adam Fedor
2002-10-08 17:05 ` Michael Snyder
2002-10-14 13:14   ` Jim Blandy
2002-10-14 20:09     ` Adam Fedor
2002-10-18 14:24       ` Elena Zannoni
2002-10-22  5:49         ` Jim Blandy
2002-10-22 14:23           ` Michael Snyder
2002-10-21 15:25       ` Andrew Cagney
2002-11-07 23:44       ` Jim Blandy
2002-11-08  7:16         ` Elena Zannoni
2002-10-08 17:07 ` Michael Snyder
2002-10-11 20:06   ` Adam Fedor
2002-10-08 17:14 ` Michael Snyder
2002-10-13 18:51   ` Adam Fedor
2002-10-08 17:16 ` Michael Snyder
2002-10-12 11:37   ` Adam Fedor
2002-10-08 17:19 ` Michael Snyder
2002-10-14 19:33   ` Adam Fedor
2002-10-16 12:16     ` Michael Snyder
2002-10-08 17:30 ` Michael Snyder
2002-10-13 19:06   ` Adam Fedor
2002-10-21 15:35   ` Andrew Cagney
2002-10-21 16:19     ` Michael Snyder
2002-10-23 12:23     ` Michael Snyder
2002-10-23 12:36       ` Andrew Cagney
2002-10-23 13:10         ` Daniel Jacobowitz
2002-10-23 14:37           ` Michael Snyder
2002-10-23 14:35         ` Michael Snyder
2002-10-08 17:34 ` Michael Snyder
2002-10-13 19:12   ` Adam Fedor

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=3D88CC99.8010803@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=fedor@doc.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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