public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "poenitz at htwm dot de" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/12806] multi-level pretty-printing Date: Wed, 28 Nov 2012 22:06:00 -0000 [thread overview] Message-ID: <bug-12806-4717-PPFmUcWtlB@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-12806-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=12806 Andre' Poenitz <poenitz at htwm dot de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |poenitz at htwm dot de --- Comment #1 from Andre' Poenitz <poenitz at htwm dot de> 2012-11-28 22:06:38 UTC --- Another option would be to move over to the "fat script" approach of pretty printing (i.e. "do all in one go, top-down"). In that case the pretty printer for an object can directly and easily decide by itself which real or which artificial children, or grand-children, or completely unrelated data, it would like to print and recursively invoke the "main" pretty print function to get "standard behaviour" for the subitems. This would also solves issues related to missing MI variable updates for items whose pretty print result takes global state or unrelated data into account (see the example give in the thread triggered by http://sourceware.org/ml/gdb-patches/2012-11/msg00027.html). -- 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.
next prev parent reply other threads:[~2012-11-28 22:06 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 ` poenitz at htwm dot de [this message] 2013-01-03 22:28 ` [Bug python/12806] " 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 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-PPFmUcWtlB@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: linkBe 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).