public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
	gdb-patches@sourceware.org
Subject: Re: [RFAv5 1/3] Implement convenience functions to examine GDB settings.
Date: Wed, 30 Oct 2019 19:43:00 -0000	[thread overview]
Message-ID: <8cf802d6-3b61-714d-3afe-c844ccf08190@redhat.com> (raw)
In-Reply-To: <20190915185314.19875-2-philippe.waroquiers@skynet.be>

On 9/15/19 7:53 PM, Philippe Waroquiers wrote:

>  void
>  _initialize_cli_cmds (void)
>  {
> @@ -2049,6 +2241,44 @@ abbreviations for commands and/or values.  E.g.:\n\
>    set_cmd_completer_handle_brkchars (c, with_command_completer);
>    add_com_alias ("w", "with", class_vars, 1);
>  
> +  add_internal_function ("_gdb_setting_str", _("\
> +$_gdb_setting_str - returns the value of a GDB setting as a string.\n\
> +Usage: $_gdb_setting_str (setting)\n\
> +\n\
> +auto-boolean values are \"off\", \"on\", \"auto\".\n\
> +boolean values are \"off\", \"on\".\n\
> +The unlimited value for integer, uinteger, zuinteger-unlimited\n\
> +settings is represented as \"unlimited\"."),

I wonder what users will think of these 
integer, uinteger, zuinteger-unlimited, etc. references.  I mean,
these are internal setting types, we don't describe them anywhere,
right?  Maybe the description here should be closer to the
manual description, telling users to loop at the documentation
of each setting to know which values to use.

> +			 gdb_setting_str_internal_fn, NULL);
> +
> +  add_internal_function ("_gdb_setting", _("\
> +$_gdb_setting - returns the value of a GDB setting.\n\
> +Usage: $_gdb_setting (setting)\n\
> +auto-boolean values are \"off\", \"on\", \"auto\".\n\
> +boolean values are \"off\", \"on\".\n\
> +The unlimited value for integer, uinteger settings is 0.\n\
> +The unlimited value for zuinteger-unlimited is -1."),

"for zuinteger-unlimited settings", I suppose.  Same thing
appears in other places below.

Otherwise LGTM.

Thanks,
Pedro Alves

  reply	other threads:[~2019-10-30 19:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-15 18:53 [RFAv5 0/3] Convenience functions $_gdb_setting/$_gdb_setting_str Philippe Waroquiers
2019-09-15 18:53 ` [RFAv5 3/3] NEWS and documentation for $_gdb_setting and $_gdb_int_setting Philippe Waroquiers
2019-10-30 19:48   ` Pedro Alves
2019-09-15 18:53 ` [RFAv5 2/3] Test the convenience functions " Philippe Waroquiers
2019-10-30 19:44   ` Pedro Alves
2019-09-15 18:53 ` [RFAv5 1/3] Implement convenience functions to examine GDB settings Philippe Waroquiers
2019-10-30 19:43   ` Pedro Alves [this message]
2019-09-29 15:28 ` PING Re: [RFAv5 0/3] Convenience functions $_gdb_setting/$_gdb_setting_str Philippe Waroquiers
2019-10-20 10:25   ` PING^2 " Philippe Waroquiers
2019-10-30 19:39 ` Pedro Alves

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=8cf802d6-3b61-714d-3afe-c844ccf08190@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    /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).