From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] python: Provide textual representation for Inferior and Objfile
Date: Wed, 12 Sep 2018 22:07:00 -0000 [thread overview]
Message-ID: <87zhwmid4p.fsf@tromey.com> (raw)
In-Reply-To: <20180912205449.12836-1-simon.marchi@ericsson.com> (Simon Marchi's message of "Wed, 12 Sep 2018 16:54:49 -0400")
>>>>> "Simon" == Simon Marchi <simon.marchi@ericsson.com> writes:
Simon> This makes printing debug traces more difficult than it should be. This
Simon> patch provides some repr() implementation for these two types (more to
Simon> come if people agree with the idea, but I want to test the water first).
I think it is a good idea.
Simon> In your opinion, does this require an announcement in NEWS and an entry
Simon> in the manual? I don't think the output of repr() should be considered
Simon> stable, as we could change it over time to make it more useful. Maybe
Simon> that should be documented?
That seems like a reasonable rule to me. One idea would be to make this
a general rule for the gdb Python layer and document it in the "Basic
Python" node.
I could go either way about a NEWS entry. It seems more like a
debugging convenience feature maybe? Dunno.
The patch looks good.
Tom
next prev parent reply other threads:[~2018-09-12 22:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 20:55 Simon Marchi
2018-09-12 22:07 ` Tom Tromey [this message]
2018-09-12 22:10 ` Simon Marchi
2018-09-12 22:50 ` [PATCH v2, doc] " Simon Marchi
2018-09-13 13:39 ` Eli Zaretskii
2018-09-13 14:37 ` Tom Tromey
2018-09-13 15:57 ` Simon Marchi
2018-09-13 15:59 ` Tom Tromey
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=87zhwmid4p.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
/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