From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, Project Archer <archer@sourceware.org>
Subject: Re: [python][patch] Add options length parameter to value.string(...)
Date: Thu, 09 Apr 2009 20:39:00 -0000 [thread overview]
Message-ID: <1239309450.30578.67.camel@localhost.localdomain> (raw)
In-Reply-To: <49DE1E5A.7080808@redhat.com>
El jue, 09-04-2009 a las 17:12 +0100, Phil Muldoon escribió:
> I think I have implemented all of your requested changes.
I looked at the patch and it seems good. I have just a few nits, I hope
you will put up with me just a tad bit more. :-)
> static PyObject *
> valpy_string (PyObject *self, PyObject *args, PyObject *kw)
> {
This function has the following comment above it:
/* Implementation of gdb.Value.string ([encoding] [, errors]) -> string
Return Unicode string with value contents. If ENCODING is not given,
the string is assumed to be encoded in the target's charset. */
Would you mind adding "[, length] to the prototype?
> + gdb_test "python print st.string (length = 0)" "" "Test string (length = 0) is empty"
Does using "" as test pattern really test for an empty line? I know that
gdb_test puts an EOL marker right after the pattern, but it doesn't put
any required pattern before the pattern...
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2009-04-09 20:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 16:54 Phil Muldoon
2009-04-06 22:14 ` Tom Tromey
2009-04-06 22:33 ` Thiago Jung Bauermann
2009-04-09 9:58 ` Phil Muldoon
2009-04-09 16:08 ` Thiago Jung Bauermann
2009-04-09 16:28 ` Phil Muldoon
2009-04-09 18:46 ` Thiago Jung Bauermann
2009-04-09 20:28 ` Phil Muldoon
2009-04-09 20:39 ` Thiago Jung Bauermann
2009-04-09 16:12 ` Phil Muldoon
2009-04-09 20:39 ` Thiago Jung Bauermann [this message]
2009-04-09 21:29 ` Phil Muldoon
2009-04-13 22:08 ` Tom Tromey
2009-04-15 9:13 ` Phil Muldoon
2009-04-15 9:37 ` Phil Muldoon
2009-04-15 12:37 ` Tom Tromey
2009-04-15 14:52 ` Phil Muldoon
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=1239309450.30578.67.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=archer@sourceware.org \
--cc=pmuldoon@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).