From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Handle var_zuinteger and var_zuinteger_unlimited from Python
Date: Fri, 27 Apr 2018 06:36:00 -0000 [thread overview]
Message-ID: <83d0ylupf7.fsf@gnu.org> (raw)
In-Reply-To: <20180426222003.9059-1-tom@tromey.com> (message from Tom Tromey on Thu, 26 Apr 2018 16:20:03 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>
> Date: Thu, 26 Apr 2018 16:20:03 -0600
>
> diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
> index ebd48fffe7..ca9114864b 100644
> --- a/gdb/doc/python.texi
> +++ b/gdb/doc/python.texi
> @@ -3800,6 +3800,20 @@ The value is a filename. This is just like
> The value is an integer. This is like @code{PARAM_INTEGER}, except 0
> is interpreted as itself.
>
> +@findex PARAM_ZUINTEGER
> +@findex gdb.PARAM_ZUINTEGER
> +@item gdb.PARAM_ZUINTEGER
> +The value is an unsigned integer. This is like @code{PARAM_INTEGER},
> +except 0 is interpreted as itself, and the value cannot be negative.
> +
> +@findex PARAM_ZUINTEGER_UNLIMITED
> +@findex gdb.PARAM_ZUINTEGER_UNLIMITED
> +@item gdb.PARAM_ZUINTEGER_UNLIMITED
> +The value is an unsigned integer. This is like @code{PARAM_ZUINTEGER},
> +except 0 is interpreted as itself, and the special value -1 should be
> +interpreted to mean ``unlimited''. Other negative values are not
> +allowed.
> +
This part is approved, but it sounds like only 1 of the 3 differences
from PARAM_ZUINTEGER should actually be mentioned, as the other 2 --
that 0 is interpreted as itself and negative values are generally not
allowed -- are already present in PARAM_ZUINTEGER. Or did I miss
something?
Thanks.
next prev parent reply other threads:[~2018-04-27 6:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 22:20 Tom Tromey
2018-04-27 6:36 ` Eli Zaretskii [this message]
2018-05-02 16:01 ` Tom Tromey
2018-05-02 16:06 ` Tom Tromey
2018-05-02 16:26 ` Eli Zaretskii
2018-05-02 16:31 ` Tom Tromey
2018-04-30 21:52 ` Joel Brobecker
2018-05-02 16:05 ` Tom Tromey
2018-05-02 16:25 ` Joel Brobecker
2018-05-02 18:16 ` Pedro Alves
2018-05-02 21:07 ` Tom Tromey
2018-05-02 21:37 ` 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=83d0ylupf7.fsf@gnu.org \
--to=eliz@gnu.org \
--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