From: Matt Rice <ratmice@gmail.com>
To: Vladimir Prus <vladimir.prus@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: GDB/MI interactive capability?
Date: Mon, 27 Apr 2015 03:28:00 -0000 [thread overview]
Message-ID: <CACTLOFqfjp5F1xPmwjbVvJ9ws6oMWSP97ZwbftMjjtJd6OxEpw@mail.gmail.com> (raw)
In-Reply-To: <mhjbdl$ae7$1@ger.gmane.org>
On Sun, Apr 26, 2015 at 11:40 AM, Vladimir Prus <vladimir.prus@gmail.com> wrote:
> On 04/22/2015 10:25 PM, Joel Brobecker wrote:
>> Another idea, which might be easier to implement, would be to use
>> a two-step approach where the first step is to return an error
>> that shows the various choices the user can choose, have the IDE
>> use that to query the user, and then have the IDE resubmit the
>> expression evaluation, this time with the choice given by the user.
>
>
> That would work just fine, I think. GDB can report the ambiguities it finds,
> and the frontend can resubmit the expression with appropriate syntax to
> disambiguate.
> I don't know whether there's appropriate syntax for Ada, in C++ a cast to
> appropriate
> type is sometimes used to select the right function, e.g.:
>
> static_cast<void (C::*)(int)>(&C::foo)
>
> is the standard example. The downside is that GDB might have to know a bit
> more about
> language than now, or a special syntax might have to be introduced.
I think it might work that instead of sending a list of stateful
numbers, it instead sent a list of explicit linespecs that can be sent
back to gdb
I'm not entirely sure (but it seems reasonable) that explicit
linespecs might avoid the ambiguity of sending a linespec to the
client which can lead to things like PR 8535
next prev parent reply other threads:[~2015-04-27 3:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 19:25 Joel Brobecker
2015-04-26 18:45 ` Vladimir Prus
2015-04-27 3:28 ` Matt Rice [this message]
2015-04-29 15:44 ` Joel Brobecker
2015-04-29 19:40 ` Vladimir Prus
2015-04-29 20:30 ` Vladimir Prus
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=CACTLOFqfjp5F1xPmwjbVvJ9ws6oMWSP97ZwbftMjjtJd6OxEpw@mail.gmail.com \
--to=ratmice@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=vladimir.prus@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).