From: Eli Zaretskii <eliz@gnu.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA][python] Add gdb.Value.string method.
Date: Thu, 05 Feb 2009 20:31:00 -0000 [thread overview]
Message-ID: <uvdrotyl8.fsf@gnu.org> (raw)
In-Reply-To: <1233839944.14735.72.camel@localhost.localdomain>
> From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
> Date: Thu, 05 Feb 2009 11:19:04 -0200
>
> > Eli> Would every Python programmer know what kind of argument strings can
> > Eli> be given for @var{encoding}? If not, perhaps a list or at least a
> > Eli> hint where to find such a list would be useful.
> >
> > We can't list the possible encodings -- not only does the list change
> > over time, but users can write their own codecs in Python.
> >
> > I suggest just hoisting the reference to Python's "string.decode"
> > method to an earlier spot in the paragraph. This should be sufficient
> > for anybody, use of the string module is common knowledge.
>
> What about the following, then?
>
> "If the optional @var{encoding} argument is given, it must be a string
> naming the encoding of the string in the @code{gdb.Value}. It accepts
> the same encodings as the corresponding argument to Python's
> @code{string.decode} method, so the Python codec machinery will be used
> to convert the string."
I'd add an example, but if you think the above is enough, I won't
object.
next prev parent reply other threads:[~2009-02-05 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 2:28 Thiago Jung Bauermann
2009-02-03 13:57 ` Thiago Jung Bauermann
2009-02-03 20:02 ` Eli Zaretskii
2009-02-04 19:45 ` Tom Tromey
2009-02-05 13:19 ` Thiago Jung Bauermann
2009-02-05 20:31 ` Eli Zaretskii [this message]
2009-02-05 21:17 ` Thiago Jung Bauermann
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=uvdrotyl8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=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