This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 1/4]: Make "python" start a standard Python prompt
Hi,
On Jul 28, 2012, at 2:53 AM, Eli Zaretskii wrote:
>> From: Khoo Yit Phang <khooyp@cs.umd.edu>
>> Date: Thu, 26 Jul 2012 22:32:15 -0400
>> Cc: Eli Zaretskii <eliz@gnu.org>, tromey@redhat.com, pmuldoon@redhat.com, gdb-patches@sourceware.org
>>
>> +@item python-interactive @r{[}@var{code}@r{]}
>> +@itemx pi @r{[}@var{code}@r{]}
>
> Why "code"? Elsewhere you used "command", which is better, IMO.
I had just copied the doc for the old "python" command, which used "code". Shall I change it there too?
>> +The @code{python-interactive} command can be used to start an
>> +interactive Python prompt.
>
> "Without an argument, the @code{python-interactive} command can be
> used ..."
>
>> +Alternatively, a single-line Python command can be given as an
>> +argument, and if the command is an expression, the result will be
>> +printed.
>
> And if the command is not an expression, what happens then?
+Alternatively, a single-line Python command can be given as an
+argument and evaluated. If the command is an expression, the result
+ will be printed; otherwise, nothing will be printed.
>> @item python @r{[}@var{code}@r{]}
>> +@itemx py @r{[}@var{code}@r{]}
>
> Again, I think "code" is not a good term here.
Yit
July 28, 2012