[PATCH 1/4]: Make "python" start a standard Python prompt
Eli Zaretskii
eliz@gnu.org
Sat Jul 28 15:05:00 GMT 2012
> From: Khoo Yit Phang <khooyp@cs.umd.edu>
> Date: Sat, 28 Jul 2012 10:34:52 -0400
> Cc: Khoo Yit Phang <khooyp@cs.umd.edu>,
> 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?
Yes, please.
> +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.
This is good, but please leave two spaces after the period that ends
the first of these two sentences.
Thanks.
More information about the Gdb-patches
mailing list