This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: 'eval' command with printf-like args, take 2
- From: Eli Zaretskii <eliz at gnu dot org>
- To: "Yakov Lerner" <iler dot ml at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sun, 24 Feb 2008 22:05:45 +0200
- Subject: Re: 'eval' command with printf-like args, take 2
- References: <f36b08ee0802240736y2ec3b356m23ec55d59ead50c2@mail.gmail.com> <f36b08ee0802240738p70696235ue9324d3c13acaf70@mail.gmail.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sun, 24 Feb 2008 17:38:55 +0200
> From: "Yakov Lerner" <iler.ml@gmail.com>
>
> + add_cmd ("eval", class_support, eval_command, _("\
> +eval \"printf-like format string\", arg1, arg2, arg3, ..., argn\n\
> +Execute gdb command from a string generated by printf-like format and\n\
> +arguments."),
The first line of the doc string cannot have commas and periods,
because GDB will stop at the first such character when it displays the
short one-line version of help for a command.
I suggest to modify this as follows:
+ add_cmd ("eval", class_support, eval_command, _("\
+Execute command generated by printf-like format and arguments.\n\
+Usage: eval \"format string\", arg1, arg2, arg3, ..., argn\n\