public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/14380] Pretty-Printing maps only takes values, interpreted alternating as key and value
Date: Wed, 01 Aug 2012 15:59:00 -0000	[thread overview]
Message-ID: <bug-14380-4717-G4V38TOX5i@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14380-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=14380

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|                            |INVALID

--- Comment #8 from Tom Tromey <tromey at redhat dot com> 2012-08-01 15:58:47 UTC ---
(In reply to comment #7)
> (In reply to comment #6)
> > If there is a bug, I think it is in nemiver.
> 
> it is not only nemiver. Eclipse CDT and Kdevelop4 behave the same.

Personally I think they are all buggy; but in reality the GUIs get
to choose how to display.  It is up to them.

The reason the "map" display hint works the the way it does is
because the first element in the tuples in a child list can really
only be strings -- but in a "map"-like data structure in the inferior,
the key could really be anything, including a complex data structure
that itself requires a pretty-printer.

When we looked at this, we judged that it was far simpler both internally
and for clients to apply special formatting after the fact to rather
ordinary varobjs, than it was to try to add a special way for some
varobjs to support non-trivial keys.

If you don't like how this looks in the CLI, simply do not use the "map"
display hint.  The kind of output you are asking for is the default.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-08-01 15:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 20:38 [Bug python/14380] New: " oliver.buchtala at googlemail dot com
2012-07-20 20:41 ` [Bug python/14380] " oliver.buchtala at googlemail dot com
2012-07-20 20:42 ` oliver.buchtala at googlemail dot com
2012-07-20 20:43 ` oliver.buchtala at googlemail dot com
2012-07-20 21:10 ` oliver.buchtala at googlemail dot com
2012-07-20 21:12 ` oliver.buchtala at googlemail dot com
2012-07-31 15:41 ` tromey at redhat dot com
2012-07-31 20:18 ` oliver.buchtala at googlemail dot com
2012-08-01 15:59 ` tromey at redhat dot com [this message]
2012-08-01 16:16 ` oliver.buchtala at googlemail dot com

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=bug-14380-4717-G4V38TOX5i@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).