Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Adam Fedor <fedor@doc.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Compile objc-lang.c, objc-exp.tab.c [1/5]
Date: Wed, 19 Feb 2003 20:27:00 -0000	[thread overview]
Message-ID: <941A376E-4448-11D7-A4B3-000A277AC1A4@doc.com> (raw)
In-Reply-To: <15955.54735.457114.404621@localhost.redhat.com>


On Wednesday, February 19, 2003, at 12:06 PM, Elena Zannoni wrote:

> Adam Fedor writes:
>> Now that I'm almost done, I finally understand the patch lingo (Thanks
>> Michael)! This is a repost of the first of five final patches for ObjC
>> suppport:
>>
>> http://sources.redhat.com/ml/gdb-patches/2003-01/msg00049.html
>>
>> The other two that I also need approval for are:
>>
>> http://sources.redhat.com/ml/gdb-patches/2003-01/msg00050.html
>> http://sources.redhat.com/ml/gdb-patches/2003-01/msg00080.html
>>
>> and two more (symtab.c, and linespec.c) will be coming soon.
>>
>> ---
>>
>> A new year brings a final push to get Objective-C support in gdb. This
>> patch enables compilation and linking of the Objective-C files. I need
>> this now since the remaining patches require so many of the 
>> Objective-C
>> functions that it would be pointless to submit them otherwise.
>>
>> 2003-01-02  Adam Fedor  <fedor@gnu.org>
>>
>> 	* Makefile.in (COMMON_OBS): Add objc-lang.o
>> 	(YYOBJ): Add objc-exp.tab.o
>> 	(maint.o, utils.o): Add $(objc_lang_h)
>> 	* maint.c (maintenance_demangle): Uncomment language_objc case.
>> 	* utils.c (fprintf_symbol_filtered): Likewise.
>> 	* parser-defs.h (start_msglist, add_msglist, end_msglist): Declare
>> 	Objective-C parsing functions (from objc-lang.c).
>
>
> I think this is just 'obvious' in a sense given the code has been
> already approved, and it is just dormant.  However, do we have
> testcases already? I think we should have a gdb.objc
> subdirectory. (sorry, i don't remember if you posted them).  I would
> feel uncomfortable enabling objc w/o having tests, even very simple
> ones, it could bitrot fast.
>
>

Yes I have one. I was going to wait till all the patches were in, 
since, AFAIK most of the tests won't pass until all my patches are in.

How should I submit it? I suppose it would have to be a tar file.


  reply	other threads:[~2003-02-19 20:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 22:06 Adam Fedor
2003-02-19 19:02 ` Elena Zannoni
2003-02-19 20:27   ` Adam Fedor [this message]
2003-02-19 21:11     ` Elena Zannoni
2003-03-20 21:27 ` Andrew Cagney
2003-03-20 21:39   ` Daniel Jacobowitz
2003-03-20 22:13     ` Andrew Cagney
2003-03-20 22:19       ` Daniel Jacobowitz
2003-03-31  2:23         ` Adam Fedor
2003-03-31 22:39           ` Andrew Cagney
2003-03-31 22:53           ` David Carlton
2003-03-31 23:03             ` David Carlton
2003-03-31 23:15             ` Adam Fedor
2003-04-01  0:31               ` Andrew Cagney
2003-04-01  0:45                 ` David Carlton
2003-04-01  4:09                 ` Adam Fedor
2003-04-01 21:31                   ` David Carlton
2003-04-01 21:38                   ` Daniel Jacobowitz
2003-03-20 22:22     ` David Ayers
2003-03-20 21:35 ` Andrew Cagney
2003-03-24 17:46   ` Adam Fedor
2003-03-24 18:25     ` Andrew Cagney
2003-03-25  2:23       ` 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=941A376E-4448-11D7-A4B3-000A277AC1A4@doc.com \
    --to=fedor@doc.com \
    --cc=ezannoni@redhat.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