Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 15/24] Introduce rename_cmd
Date: Thu, 30 May 2019 10:22:00 -0000	[thread overview]
Message-ID: <1559211760.1454.35.camel@skynet.be> (raw)
In-Reply-To: <fbdeebea-a318-6a51-98b3-5deba9e21930@redhat.com>

On Wed, 2019-05-29 at 19:30 +0100, Pedro Alves wrote:
> On 5/29/19 5:03 PM, Pedro Alves wrote:
> 
> > There are other ways to implement this.  I could move the
> > "raw-frame-arguments" option_def out of the frame_print_option_defs
> > array, so that it doesn't get installed as a command, and leave the
> > "set print raw frame-arguments" add_setshow... call in place.
> > I guess it wouldn't be a big deal.
> 
> So turns out the change would be pretty simple.
> 
> I'm undecided which version to use...  I suppose this version
> is simpler and a little bit more efficient.  Preferences?

As 'frame-arguments' is the only command that uses the prefix 'set print raw'
and that this prefix should not be used for further options, I would mark
'set print raw' obsolete, to avoid an inconsistency (at user level)
only for this option.
But not a big deal ...

> 
> From fcbbc6a33276a8ec59425174f6868379d0a239a3 Mon Sep 17 00:00:00 2001
> From: Pedro Alves <palves@redhat.com>
> Date: Wed, 29 May 2019 19:04:05 +0100
> Subject: [PATCH] no-rename
> 
> ---
>  gdb/stack.c | 44 ++++++++++++++++++++++++--------------------
>  1 file changed, 24 insertions(+), 20 deletions(-)
> 
> diff --git a/gdb/stack.c b/gdb/stack.c
> index 3054c797c74..2c58b0d728b 100644
> --- a/gdb/stack.c
> +++ b/gdb/stack.c
> @@ -126,16 +126,16 @@ or both.  Note that one or both of these values may be <optimized out>."),
>      N_("Show printing of non-scalar frame arguments"),
>      NULL /* help_doc */
>    },
> +};
>  
> -  boolean_option_def {
> -    "raw-frame-arguments",
> -    [] (frame_print_options *opt) { return &opt->print_raw_frame_arguments; },
> -    NULL, /* show_cmd_cb */
> -    N_("Set whether to print frame arguments in raw form."),
> -    N_("Show whether to print frame arguments in raw form."),
> -    N_("If set, frame arguments are printed in raw form, bypassing any\n\
> -pretty-printers for that value.")
> -  },
> +/* The "raw-frame-arguments" option.  Defined separately because the
> +   corresponding "set" command is called "set print raw
> +   frame-arguments", with space instead of dash.  */
> +static const boolean_option_def raw_frame_arguments_option_def {
> +  "raw-frame-arguments",
> +  [] (frame_print_options *opt) { return &opt->print_raw_frame_arguments; },
> +  NULL, /* show_cmd_cb */
> +  N_("Set whether to print frame arguments in raw form."),
>  };
>  
>  /* Options for the "backtrace" command.  */
> @@ -2015,13 +2015,14 @@ backtrace_command_1 (const frame_print_options &fp_opts,
>  /* Create an option_def_group array grouping all the "backtrace"
>     options, with FP_OPTS, BT_CMD_OPT, SET_BT_OPTS as contexts.  */
>  
> -static inline std::array<gdb::option::option_def_group, 3>
> +static inline std::array<gdb::option::option_def_group, 4>
>  make_backtrace_options_def_group (frame_print_options *fp_opts,
>  				  backtrace_cmd_options *bt_cmd_opts,
>  				  set_backtrace_options *set_bt_opts)
>  {
>    return {{
>      { {frame_print_option_defs}, fp_opts },
> +    { raw_frame_arguments_option_def.def (), fp_opts },
>      { {set_backtrace_option_defs}, set_bt_opts },
>      { {backtrace_command_option_defs}, bt_cmd_opts }
>    }};
> @@ -3288,14 +3289,17 @@ source line."),
>      (class_stack, &user_frame_print_options,
>       frame_print_option_defs, &setprintlist, &showprintlist);
>  
> -  /* The above installs a "set print raw-frame-arguments" command,
> -     because there's an option called "print -raw-frame-arguments".
> -     Rename the command to "set print raw frame-arguments" (space
> -     instead of dash), to keep backward compatibility -- the "raw
> -     frame-arguments" command already existed when print options were
> -     first added.  */
> -  rename_cmd ("raw-frame-arguments", &setprintlist,
> -	      "frame-arguments", &setprintrawlist);
> -  rename_cmd ("raw-frame-arguments", &showprintlist,
> -	      "frame-arguments", &showprintrawlist);
> +  /* This one is not defined by the add_setshow_cmds_for_options call
> +     above, because the option is called "raw-frame-arguments", while
> +     the command is called "set print raw frame-arguments", with space
> +     instead of dash.  */
> +  add_setshow_boolean_cmd ("frame-arguments", no_class,
> +			   &user_frame_print_options.print_raw_frame_arguments,
> +			   _("\
> +Set whether to print frame arguments in raw form."), _("\
> +Show whether to print frame arguments in raw form."), _("\
> +If set, frame arguments are printed in raw form, bypassing any\n\
> +pretty-printers for that value."),
> +			   NULL, NULL,
> +			   &setprintrawlist, &showprintrawlist);
>  }


  reply	other threads:[~2019-05-30 10:22 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 20:53 [PATCH 00/24] gdb::option framework, "print -OPT", other cmd options Pedro Alves
2019-05-22 20:53 ` [PATCH 08/24] gdb.base/settings.exp: Fix comment typo Pedro Alves
2019-05-24 11:40   ` Pedro Alves
2019-05-22 20:53 ` [PATCH 03/24] Fix TID parser bug Pedro Alves
2019-05-22 20:53 ` [PATCH 07/24] Remove "show" command completers Pedro Alves
2019-05-23 19:28   ` Sergio Durigan Junior
2019-05-24 11:25     ` Pedro Alves
2019-05-24 14:21       ` Sergio Durigan Junior
2019-05-22 20:53 ` [PATCH 11/24] number_or_range_parser::get_number, don't treat "1 -" as a range Pedro Alves
2019-05-22 20:53 ` [PATCH 04/24] Make check_for_argument skip whitespace after arg itself Pedro Alves
2019-05-22 20:53 ` [PATCH 18/24] lib/completion-support.exp: Add test_gdb_completion_offers_commands Pedro Alves
2019-05-22 20:53 ` [PATCH 19/24] Introduce complete_command Pedro Alves
2019-05-22 20:53 ` [PATCH 15/24] Introduce rename_cmd Pedro Alves
2019-05-25 19:58   ` Philippe Waroquiers
2019-05-29 16:03     ` Pedro Alves
2019-05-29 18:30       ` Pedro Alves
2019-05-30 10:22         ` Philippe Waroquiers [this message]
2019-05-30 20:01           ` Pedro Alves
2019-05-22 20:54 ` [PATCH 20/24] Make "frame apply" support -OPT options Pedro Alves
2019-05-25 20:12   ` Philippe Waroquiers
2019-05-29 15:13     ` Pedro Alves
2019-05-29 15:25       ` Pedro Alves
2019-05-22 20:54 ` [PATCH 14/24] Migrate rest of compile commands to new options framework Pedro Alves
2019-05-22 20:54 ` [PATCH 01/24] Fix latent bug in custom word point completion handling Pedro Alves
2019-05-22 20:54 ` [PATCH 22/24] Make "thread apply" use the gdb::option framework Pedro Alves
2019-05-25 20:24   ` Philippe Waroquiers
2019-05-29 15:38     ` Pedro Alves
2019-05-22 20:54 ` [PATCH 10/24] boolean/auto-boolean commands, make "o" ambiguous Pedro Alves
2019-05-22 20:54 ` [PATCH 02/24] Fix latent bug with custom word point completers Pedro Alves
2019-05-22 20:54 ` [PATCH 09/24] New set/show testing framework (gdb.base/settings.exp) Pedro Alves
2019-05-23  4:15   ` Eli Zaretskii
2019-05-22 20:54 ` [PATCH 12/24] Introduce generic command options framework Pedro Alves
2019-05-25  7:43   ` Philippe Waroquiers
2019-05-25 10:31     ` Pedro Alves
2019-05-22 20:54 ` [PATCH 21/24] "thread apply 1 -- -" vs "frame apply level 0 -- -" Pedro Alves
2019-05-22 20:54 ` [PATCH 06/24] Fix "set enum-command value garbage" Pedro Alves
2019-05-23 19:13   ` Sergio Durigan Junior
2019-05-24 11:39     ` Pedro Alves
2019-05-22 20:54 ` [PATCH 05/24] Allow "unlimited" abbreviations Pedro Alves
2019-05-22 20:58 ` [PATCH 13/24] Make "print" and "compile print" support -OPT options Pedro Alves
2019-05-24 19:49   ` Sergio Durigan Junior
2019-05-25 10:10     ` Pedro Alves
2019-05-25 10:37       ` Andreas Schwab
2019-05-22 20:58 ` [PATCH 16/24] Make "backtrace" " Pedro Alves
2019-05-22 21:00 ` [PATCH 17/24] "backtrace full/no-filters/hide" completer Pedro Alves
2019-05-22 21:00 ` [PATCH 24/24] NEWS and manual changes for command options changes Pedro Alves
2019-05-23  4:31   ` Eli Zaretskii
2019-05-23 15:01     ` Pedro Alves
2019-05-23 15:07       ` Eli Zaretskii
2019-05-23 15:31         ` Pedro Alves
2019-05-25 20:40   ` Philippe Waroquiers
2019-05-29 16:03     ` Pedro Alves
2019-05-22 21:03 ` [PATCH 23/24] Delete parse_flags/parse_flags_qcs Pedro Alves
2019-05-22 21:46 ` [PATCH 00/24] gdb::option framework, "print -OPT", other cmd options Pedro Alves
2019-05-24 19:58 ` Sergio Durigan Junior

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=1559211760.1454.35.camel@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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