From: Adam Fedor <fedor@doc.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Michael Snyder <msnyder@redhat.com>,
GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [PATCH] Handle ObjC OPS in eval.c
Date: Sun, 20 Apr 2003 03:42:00 -0000 [thread overview]
Message-ID: <3EA21739.2030403@doc.com> (raw)
In-Reply-To: <16021.59784.477170.598470@localhost.redhat.com>
Elena Zannoni wrote:
> Adam Fedor writes:
> >
> >
> > Elena Zannoni wrote:
> > [...]
> > >
> > > I think we need more comments, I guess stret means structure return?
> > > What are these methods used for? Also can you add a high level
> > > description of how these dispatchers get into the picture?
> > >
> >
> > Here's a better documented and slightly cleaned-up patch.
> > 2003-03-04 Adam Fedor <fedor@gnu.org>
>
> I think it's ok. Except I don't like to introduce more #if0 code with new code.
> Do we really need that part?
>
I bet no one would complain if I took it out.
The larger problem I have, though, is changing the patch so that I can
call the objc-lang functions indirectly, so that objc-lang.o does not
have to be linked in. That seems like a pain.
I think it would be easier to split objc-lang.c into two parts. One that
is architecture independant that I could link in now, and the other
acitecture dependant part (which is already handled via the language
vector). Anything wrong with that?
next prev parent reply other threads:[~2003-04-20 3:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 20:27 Adam Fedor
2003-01-31 3:07 ` Michael Snyder
2003-02-07 18:31 ` Adam Fedor
2003-02-07 22:04 ` Andrew Cagney
2003-02-13 4:05 ` Adam Fedor
2003-02-19 20:05 ` Elena Zannoni
2003-03-05 5:06 ` Adam Fedor
2003-04-10 21:56 ` Elena Zannoni
2003-04-20 3:42 ` Adam Fedor [this message]
2003-04-21 4:14 ` Daniel Jacobowitz
2003-04-21 16:26 ` Elena Zannoni
2003-04-21 16:47 ` Adam Fedor
2003-04-21 16:51 ` Daniel Jacobowitz
2003-04-21 17:09 ` Elena Zannoni
2003-04-21 18: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=3EA21739.2030403@doc.com \
--to=fedor@doc.com \
--cc=ezannoni@redhat.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