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
> 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
>
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -17,6 +17,14 @@
> maint info bfds
> List the BFDs known to GDB.
>
> +python-interactive [command]
> +pi [command]
> + Start a Python interactive prompt, or evaluate the optional command
> + and print the result of expressions.
> +
> +py [command]
> + "py" is a new alias for "python".
> +
> *** Changes in GDB 7.5
This part is OK.
> +@item python-interactive @r{[}@var{code}@r{]}
> +@itemx pi @r{[}@var{code}@r{]}
Why "code"? Elsewhere you used "command", which is better, IMO.
> +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?
> @item python @r{[}@var{code}@r{]}
> +@itemx py @r{[}@var{code}@r{]}
Again, I think "code" is not a good term here.