This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA][python] Add gdb.Value.string method.
- From: Tom Tromey <tromey at redhat dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Thiago Jung Bauermann <bauerman at br dot ibm dot com>, gdb-patches at sourceware dot org
- Date: Wed, 04 Feb 2009 12:45:32 -0700
- Subject: Re: [RFA][python] Add gdb.Value.string method.
- References: <1230949647.8380.145.camel@localhost.localdomain> <1233669417.14735.14.camel@localhost.localdomain> <uab93uw54.fsf@gnu.org>
- Reply-to: tromey at redhat dot com
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>> > +If the optional @var{encoding} argument is given, it must be a string
>> > +naming the encoding of the string in the @code{gdb.Value}.
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.
Tom