From: Keith Seitz <keiths@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [5/5] fix test suite for MI output
Date: Tue, 15 May 2012 17:14:00 -0000 [thread overview]
Message-ID: <4FB28EE3.6090807@redhat.com> (raw)
In-Reply-To: <87pqa6v8fo.fsf@fleche.redhat.com>
On 05/14/2012 01:01 PM, Tom Tromey wrote:
> I'm not sure whether this is reasonable to do or not, so I pulled this
> patch out separately.
Preface: I'm not an MI user, but I do use varobj. This isn't a protest
or other demand for action, but I felt compelled to add my $2E-10, in
hopes of coaxing other users to offer an opinion.
> It is not too hard to fix varobj to disable this new setting, if that is
> preferable for some reason.
I really don't like this. UIs will now display arrays (what about other
aggregate types like struct pointers?) this way, and in the context of
varobj, it provides no additional information that the UI isn't already
providing users:
+ my_array (int [10]) 0x12345678 <my_array>
Keith
next prev parent reply other threads:[~2012-05-15 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 20:01 Tom Tromey
2012-05-15 17:14 ` Keith Seitz [this message]
2012-05-15 17:27 ` Tom Tromey
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=4FB28EE3.6090807@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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