Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: "gdb-patches@sources.redhat.com" <gdb-patches@sources.redhat.com>
Subject: Re: [RFC]: Disallow ObjC search when resetting breakpoint.
Date: Thu, 06 Nov 2003 21:03:00 -0000	[thread overview]
Message-ID: <16298.46854.491572.438957@localhost.redhat.com> (raw)
In-Reply-To: <20031106202659.GA31400@nevyn.them.org>

Daniel Jacobowitz writes:
 > On Thu, Nov 06, 2003 at 03:19:42PM -0500, Elena Zannoni wrote:
 > > Hmm, not sure about this. Maybe it is the code that follows your new
 > > 'if' in decode_line_1 that should be changed.  Definitely saving more
 > > info in the breakpoints would be helpful.
 > > 
 > > Question: how does this work for overloaded functions in c++?
 > > decode_line_1 calls decode_compounds, which calls find_method, which
 > > calls decode_line_2, which asks the user. I would think a similar
 > > problem arises there. If not, then can we make objc do the same thing
 > > that c++ does?
 > 
 > For C++, the problem doesn't arise.  I think that ObjC's problem is
 > that one of the options is the same as the ambiguous form; C++ can
 > always generate a description of which overloaded function is meant. 
 > Well, except when it can't.
 > 

ah, right.

 > I have some ideas on how to address this, but I haven't even created
 > the branch for it yet :)
 > 

Ok I was hoping you'd say that! :-)
Let's wait then on this.

elena


 > -- 
 > Daniel Jacobowitz
 > MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2003-11-06 21:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17  4:02 Adam Fedor
2003-11-06 20:19 ` Elena Zannoni
2003-11-06 20:27   ` Daniel Jacobowitz
2003-11-06 21:03     ` Elena Zannoni [this message]

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=16298.46854.491572.438957@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=drow@mvista.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