Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] python: Provide textual representation for Inferior and Objfile
Date: Wed, 12 Sep 2018 22:10:00 -0000	[thread overview]
Message-ID: <a0b0cc8604587204f2790deadaf5b256@polymtl.ca> (raw)
In-Reply-To: <87zhwmid4p.fsf@tromey.com>

On 2018-09-12 18:07, Tom Tromey wrote:
>>>>>> "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.

Good idea, a blanket warning (for string repr of all object types) in 
there should be enough.  I'll do it that.

> I could go either way about a NEWS entry.  It seems more like a
> debugging convenience feature maybe?  Dunno.

That's what I think too.

Thanks,

Simon


  reply	other threads:[~2018-09-12 22:10 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
2018-09-12 22:10   ` Simon Marchi [this message]
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=a0b0cc8604587204f2790deadaf5b256@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.com \
    --cc=tom@tromey.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