From: Vladimir Prus <vladimir@codesourcery.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sources.redhat.com
Subject: Re: [MI] -stack-list-variables
Date: Tue, 22 Sep 2009 05:31:00 -0000 [thread overview]
Message-ID: <200909220931.27493.vladimir@codesourcery.com> (raw)
In-Reply-To: <19127.63969.180199.561232@totara.tehura.co.nz>
On Tuesday 22 September 2009 Nick Roberts wrote:
> > > 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.
>
> That's exactly what I have done.
Hmm, I must have missed. You never said that you want to implement this-and-that
in Emacs, and explained why and how. What you said was you consider the separation
"useful", which is considerably more weaker statement.
Are you actually planning on implementing locals/arg separation in Emacs in
observable timeframe?
> and:
>
> > I am frankly surprised by the amount of support for this feature, and
> > the fact that this support say this is harmless, and possibly
> > useful, but does not name any single frontend that actually separates
> > arguments from "true" locals.
>
> I'm not sure that `proof by example' should be necessary. but here's an
> example showing Totalview separate the two:
>
> http://upc.lbl.gov/docs/user/ProcessWindow.png
>
> Totalview is probably the world's best C/C++ debugger
Uhm, this is very subjective statement (though you seem to use Totalview as
example regularly). Looking on the screenshot, I am not impressed.
> (apart fron GDB, of
> course!). I'm sure that if their users didn't want this feature, Etnus would
> remove it.
I am not aware how marketing/management/design works at that company, so I
cannot comment on this.
> As a maintainer I would try to accommodate such requests and reserve my
> judgements for technical matters.
I disagree. Sensible frontend interface is only possible if we (or I) understand
specific use cases that are supported, and how they are supposed, as opposed to
working from requests to add some information to some command.
- Volodya
next prev parent reply other threads:[~2009-09-22 5:31 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
2009-09-21 22:10 ` Nick Roberts
2009-09-22 5:31 ` Vladimir Prus [this message]
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=200909220931.27493.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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