From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Andrew Oakley <andrew@ado.is-a-geek.net>
Subject: Re: Python API - nested pretty printers MI implications
Date: Mon, 15 Aug 2011 12:58:00 -0000 [thread overview]
Message-ID: <201108151357.50298.pedro@codesourcery.com> (raw)
In-Reply-To: <20110814171023.19db4f49@ado-gentoo>
On Sunday 14 August 2011 17:10:23, Andrew Oakley wrote:
> def children(self):
> yield ("normal variable", "some value")
> yield ("phony group 1", inner_pretty_printer(...))
> yield ("phony group 2", inner_pretty_printer(...))
>
> This seems to work well but I'm not quite sure how to handle the for MI.
>
> As far as I can tell I need to create "fake" varobj structures with no
> underlying value or type (because I don't have one).
I'm not very familiar with the pretty printing stuff, but,
doesn't something like this work nowadays?
class phony_value:
...
/* extend Value */
class phony_value_pretty_printer:
def __init__(self, ...):
...
def new_phony(outer, whatnot):
/* return new phony value for outer */
...
class outer_pretty_printer:
def __init__(self, val):
...
def to_string(self):
...
def children(self):
yield ("normal variable", "some value")
yield ("phony group 1", new_phony(1))
yield ("phony group 2", new_phony(2))
That is, create a specialized Value class and install the pretty
printer for that _value_.
--
Pedro Alves
next prev parent reply other threads:[~2011-08-15 12:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 16:11 Andrew Oakley
2011-08-14 22:18 ` Daniel Jacobowitz
2011-08-15 12:36 ` André Pönitz
2011-08-15 13:26 ` Pedro Alves
2011-08-15 14:33 ` André Pönitz
2011-08-15 14:49 ` Pedro Alves
2011-08-15 15:36 ` André Pönitz
2011-08-16 22:12 ` Andrew Oakley
2011-08-16 22:23 ` [PATCH] Allow nested python pretty printers andrew
2011-08-17 9:56 ` Phil Muldoon
2011-08-17 13:28 ` Andrew Oakley
2011-08-15 12:58 ` Pedro Alves [this message]
2011-08-15 14:06 ` Python API - nested pretty printers MI implications Andrew Oakley
2011-08-15 14:30 ` Pedro Alves
2011-08-16 22:12 ` Andrew Oakley
2011-08-17 12:49 ` Pedro Alves
2011-08-17 18:31 ` Andrew Oakley
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=201108151357.50298.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=andrew@ado.is-a-geek.net \
--cc=gdb@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