This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] Handle var_zuinteger and var_zuinteger_unlimited from Python
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Tom Tromey <tom at tromey dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 27 Apr 2018 09:35:56 +0300
- Subject: Re: [RFA] Handle var_zuinteger and var_zuinteger_unlimited from Python
- References: <20180426222003.9059-1-tom@tromey.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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.