From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA 5/8] Allow defining a user command inside a user command
Date: Tue, 24 Apr 2018 16:43:00 -0000 [thread overview]
Message-ID: <ff93efba-0acd-132b-ae03-231b7d55cdbb@redhat.com> (raw)
In-Reply-To: <20180419191539.661-6-tom@tromey.com>
On 04/19/2018 08:15 PM, Tom Tromey wrote:
> build_command_line (enum command_control_type type, const char *args)
> {
> if ((args == NULL || *args == '\0')
> - && (type == if_control || type == while_control))
> - error (_("if/while commands require arguments."));
> + && (type == if_control || type == while_control
> + || type == define_control))
> + error (_("if/while/define commands require arguments."));
I'd vote for splitting those up:
if (args == NULL || *args == '\0')
{
switch (type)
{
case if_control:
error (_("if commands require arguments."));
case while_control:
error (_("while commands require arguments."));
case define_control:
error (_("define commands require arguments."));
}
}
> +/* Define a user-defined command. If COMMANDS is NULL, then this is
> + an interactive call and the commands will be read from the user.
Isn't this conflating top-level "define" command, with interactive
input? I imagine that a top-level "define" command in e.g., gdbinit will
considered "interactive call" according to the above, while in truth,
it's not really interactive, according to FROM_TTY.
> + Otherwise, it is a "define" command in a script and the commands
> + are provided.
Similarly, can't you write a "define" command inside a "define"
command interactively on the command line?
>In the non-interactive case, various prompts and
> + warnings are disabled. */
> +
> static void
> -define_command (const char *comname, int from_tty)
> +do_define_command (const char *comname, int from_tty,
> + const counted_command_line *commands)
> {
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-04-24 16:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 19:16 [RFA 0/8] Various command-related improvements Tom Tromey
2018-04-19 19:16 ` [RFA 6/8] Use function_view in cli-script.c Tom Tromey
2018-04-22 19:02 ` Pedro Alves
2018-04-24 23:38 ` Tom Tromey
2018-04-19 19:16 ` [RFA 7/8] Allow breakpoint commands to be set from Python Tom Tromey
2018-04-19 19:31 ` Eli Zaretskii
2018-04-24 16:43 ` Pedro Alves
2018-04-19 19:16 ` [RFA 8/8] Let gdb.execute handle multi-line commands Tom Tromey
2018-04-19 19:32 ` Eli Zaretskii
2018-04-24 16:44 ` Pedro Alves
2018-04-19 19:16 ` [RFA 2/8] Use counted_command_line everywhere Tom Tromey
2018-04-24 16:43 ` Pedro Alves
2018-04-24 23:11 ` Tom Tromey
2018-04-24 23:18 ` Tom Tromey
2018-04-19 19:16 ` [RFA 5/8] Allow defining a user command inside a user command Tom Tromey
2018-04-24 16:43 ` Pedro Alves [this message]
2018-04-24 23:24 ` Tom Tromey
2018-04-19 19:16 ` [RFA 4/8] Constify prompt argument to read_command_lines Tom Tromey
2018-04-24 16:43 ` Pedro Alves
2018-04-19 19:16 ` [RFA 3/8] Make print_command_trace varargs Tom Tromey
2018-04-24 16:43 ` Pedro Alves
2018-04-19 19:16 ` [RFA 1/8] Allocate cmd_list_element with new Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff93efba-0acd-132b-ae03-231b7d55cdbb@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).