From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Python pretty-printing [2/6]
Date: Fri, 03 Apr 2009 20:36:00 -0000 [thread overview]
Message-ID: <1238790991.3236.75.camel@localhost.localdomain> (raw)
In-Reply-To: <m31vsabn5q.fsf@fleche.redhat.com>
El jue, 02-04-2009 a las 18:23 -0600, Tom Tromey escribió:
> >>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
> Thiago> Also, just to check: the lack of testcases is because you believe this
> Thiago> code is tested enough with python-prettyprint.exp in a later patch?
>
> You know, I am not sure. This class doesn't provide much behavior
> yet. And, the most important bits are tested by the pretty-printer.
> I'm inclined not to bother, but if you (or anybody) thinks it is
> important, I suppose I can whip something up.
Well, my policy with python testcases has been to at least smoke-test
all of the API supported by GDB. That way, if we make an API-breaking
change, at least one testcase will fail.
I won't insist that it is important to do this, since I believe it's not
hard to spot API changes by looking at a patch.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
prev parent reply other threads:[~2009-04-03 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 20:55 Tom Tromey
2009-04-02 22:29 ` Thiago Jung Bauermann
2009-04-03 0:23 ` Tom Tromey
2009-04-03 0:47 ` Tom Tromey
2009-04-03 15:06 ` Eli Zaretskii
2009-04-06 19:25 ` Tom Tromey
2009-04-06 20:41 ` Eli Zaretskii
2009-04-03 20:36 ` Thiago Jung Bauermann [this message]
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=1238790991.3236.75.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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