From: Tom Tromey <tromey@redhat.com>
To: "André Pönitz" <andre.poenitz@mathematik.tu-chemnitz.de>
Cc: xgsa <xgsa@yandex.ua>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
Vladimir_Prus@mentor.com
Subject: Re: [patch] Use the string returned by pretty printer for MI varobjs instead of "{...}"
Date: Thu, 17 May 2012 15:27:00 -0000 [thread overview]
Message-ID: <87vcjultey.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120517121923.GB6350@klara.mpi.htwm.de> (=?utf-8?Q?=22Andr?= =?utf-8?Q?=C3=A9_P=C3=B6nitz=22's?= message of "Thu, 17 May 2012 14:19:23 +0200")
>>>>> "André" == André Pönitz <andre.poenitz@mathematik.tu-chemnitz.de> writes:
André> 'git blame' thinks you added it in September 2009, so gdb 7.0 is
André> probably the first one that has it. Calling code "broken" just
André> because it handles (also...) "legacy" setups is a bit of a stretch
André> in my opinion.
We're only talking about dynamic varobjs here, which the MI user must
explicitly request. Checking a dynamic varobj for "{...}" has always
been wrong, since they were first introduced.
Looking at this for non-dynamic varobjs... well, I wouldn't do that, but
it isn't relevant.
André> If you really want to read more into the comment than what was
André> actually written, then perhaps a friendly nudge to adapt the
André> documentation to existing practice.
As far as I know the documentation is correct.
Tom
prev parent reply other threads:[~2012-05-17 15:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 20:17 xgsa
2012-04-27 18:51 ` xgsa
2012-05-03 6:51 ` xgsa
2012-05-03 14:57 ` Joel Brobecker
2012-05-08 6:40 ` xgsa
2012-05-15 5:45 ` xgsa
2012-05-04 7:45 ` Eli Zaretskii
2012-05-15 16:28 ` Tom Tromey
2012-05-16 1:05 ` André Pönitz
2012-05-16 14:59 ` Tom Tromey
2012-05-17 12:19 ` André Pönitz
2012-05-17 12:58 ` Vladimir Prus
2012-05-17 19:07 ` xgsa
2012-05-21 19:04 ` xgsa
2012-05-17 15:27 ` Tom Tromey [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=87vcjultey.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=Vladimir_Prus@mentor.com \
--cc=andre.poenitz@mathematik.tu-chemnitz.de \
--cc=gdb-patches@sourceware.org \
--cc=xgsa@yandex.ua \
/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