From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'Joel Brobecker'" <brobecker@adacore.com>,
"'Vladimir Prus'" <vladimir@codesourcery.com>
Cc: "'gdb-patches@sources.redhat.com'" <gdb-patches@sources.redhat.com>
Subject: RE: [MI] -stack-list-variables
Date: Mon, 21 Sep 2009 17:03:00 -0000 [thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC51564F0699@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <20090921162732.GZ8910@adacore.com>
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org
> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Joel Brobecker
> Sent: Monday, September 21, 2009 12:28 PM
> To: Vladimir Prus
> Cc: gdb-patches@sources.redhat.com
> Subject: Re: [MI] -stack-list-variables
>
>>> But what would happen the day a front-end starts caring? Are they
>>> going to have to send 2 MI commands to get the info?
>>
>> No. The frontend author would write an email to gdb@sources.redhat.com,
>> explaining the reasons, and a new field will be added as result. That's
>> how I'd prefer MI to evolve, as opposed to adding information ahead of
>> the time.
A disadvantage with this approach is that this feature would only be
available in the GDB release that occurred after the feature request.
A frontend that would request the feature could not offer the same
functionality with older GDBs.
We can't prepare for everything of course, but in this case, why not?
Just my thoughts
Marc
next prev parent reply other threads:[~2009-09-21 17:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 10:12 Vladimir Prus
2009-09-19 10:13 ` Vladimir Prus
2009-09-19 10:38 ` Eli Zaretskii
2009-09-19 11:15 ` Vladimir Prus
2009-09-19 15:45 ` Joel Brobecker
2009-09-19 15:46 ` Joel Brobecker
2009-09-19 22:41 ` -stack-list-variables Nick Roberts
2009-09-20 6:18 ` [MI] -stack-list-variables Vladimir Prus
2009-09-20 22:05 ` Nick Roberts
2009-09-21 5:14 ` Vladimir Prus
2009-09-21 7:13 ` Nick Roberts
2009-09-21 7:39 ` Vladimir Prus
2009-09-21 15:29 ` Joel Brobecker
2009-09-21 16:02 ` Vladimir Prus
2009-09-21 16:27 ` Joel Brobecker
2009-09-21 16:54 ` Vladimir Prus
2009-09-21 17:04 ` Tom Tromey
2009-09-21 17:17 ` Vladimir Prus
2009-09-21 17:24 ` Tom Tromey
2009-09-21 17:03 ` Marc Khouzam [this message]
2009-09-21 22:10 ` Nick Roberts
2009-09-22 5:31 ` Vladimir Prus
2009-09-22 14:50 ` Daniel Jacobowitz
2009-09-29 6:35 ` Vladimir Prus
2009-09-29 23:27 ` Nick Roberts
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=F7CE05678329534C957159168FA70DEC51564F0699@EUSAACMS0703.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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