From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Python pretty-printing [5/6]
Date: Thu, 09 Apr 2009 00:29:00 -0000 [thread overview]
Message-ID: <m3r602wtxx.fsf@fleche.redhat.com> (raw)
In-Reply-To: <ueiw9iwqp.fsf@gnu.org> (Eli Zaretskii's message of "Fri\, 03 Apr 2009 18\:26\:54 +0300")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Tom> It adds a new "/r" ("raw") option to the print command family.
Eli> But this change in behavior is not documented in the docs patch,
Eli> right?
Thanks, I forgot to merge that hunk.
It will show up in the next revision of this patch.
Tom> +A pretty-printer is an object that implements a specific interface.
Tom> +There is no predefined base class for pretty-printers.
Eli> Is it possible to expand this a bit?
I added a real-world example here.
Tom> Then @value{GDBN} prints this value; this may possibly
Tom> +result in a call to another pretty-printer. If the result is not
Tom> +convertible to @code{gdb.Value}, an exception is raised.
Eli> Should we say what exception is raised?
For the time being I would rather not. I think we will probably
introduce our own exception types at some point, so I'd rather not
make a promise here.
Tom
next prev parent reply other threads:[~2009-04-09 0:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 20:57 Tom Tromey
2009-04-03 15:29 ` Eli Zaretskii
2009-04-09 0:29 ` Tom Tromey [this message]
2009-04-04 16:39 ` Thiago Jung Bauermann
2009-04-09 0:52 ` Tom Tromey
2009-04-09 15:00 ` Thiago Jung Bauermann
2009-04-09 15:19 ` Phil Muldoon
2009-04-09 15:41 ` Thiago Jung Bauermann
2009-04-09 16:18 ` Tom Tromey
2009-04-09 15:44 ` Tom Tromey
2009-04-09 19:37 ` Tom Tromey
2009-04-09 22:09 ` Thiago Jung Bauermann
2009-04-09 22:36 ` Tom Tromey
2009-04-07 18:32 ` Joel Brobecker
2009-04-07 18:41 ` Tom Tromey
2009-04-07 20:38 ` Joel Brobecker
2009-04-09 1:08 ` Tom Tromey
2009-04-09 7:40 ` Eli Zaretskii
2009-04-09 16:16 ` Tom Tromey
2009-04-09 16:41 ` Eli Zaretskii
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=m3r602wtxx.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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