public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/12806] multi-level pretty-printing
Date: Thu, 31 Aug 2023 19:24:11 +0000	[thread overview]
Message-ID: <bug-12806-4717-eGIcxaZ4zV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12806-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=12806

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Andre' from comment #1)
> Another option would be to move over to the "fat script" approach of pretty
> printing (i.e. "do all in one go, top-down").

I want to do something that's also relatively useful to DAP.
In DAP, the child of a variable may itself be a variable.
So separate objects are probably the most straightforward.
This is similar to varobj but not as bizarre.

A one-shot, full-tree approach loses laziness, which is part of DAP.
However it could be done "either direction", either by having an
object that hands tearoffs to gdb, or by eagerly iterating over
children.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-08-31 19:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 18:14 [Bug python/12806] New: " tromey at redhat dot com
2012-11-28 22:06 ` [Bug python/12806] " poenitz at htwm dot de
2013-01-03 22:28 ` poenitz at htwm dot de
2022-06-11 19:32 ` tromey at sourceware dot org
2023-08-31 16:58 ` tromey at sourceware dot org
2023-08-31 19:24 ` tromey at sourceware dot org [this message]
2023-08-31 20:01 ` tromey at sourceware dot org
2023-08-31 20:02 ` tromey at sourceware dot org
2023-09-26 15:35 ` tromey at sourceware dot org
2023-09-26 15:38 ` tromey at sourceware dot org

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-12806-4717-eGIcxaZ4zV@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).