From: Doug Evans <dje@google.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] var_zuinteger_unlimited and 'set listsize'.
Date: Thu, 02 Aug 2012 08:34:00 -0000 [thread overview]
Message-ID: <CADPb22QQeme8nTonPJ-TjgPQvC9WuzrJuiP0PHV_jbd1at7tLQ@mail.gmail.com> (raw)
In-Reply-To: <1343829334-3151-2-git-send-email-yao@codesourcery.com>
On Wed, Aug 1, 2012 at 6:55 AM, Yao Qi <yao@codesourcery.com> wrote:
> Hi,
> This patch is to add new var_types 'var_zuinteger_unlimited' and
> fix 'set listsize'.
>
> gdb:
>
> 2012-08-01 Yao Qi <yao@codesourcery.com>
> Mark Kettenis <kettenis@gnu.org>
>
> * cli/cli-decode.c (add_setshow_zuinteger_unlimited_cmd): New.
> * cli/cli-setshow.c (do_setshow_command): Handle case
> 'var_zuinteger_unlimited'.
> (do_setshow_command): Check the range for var_uinteger and
> var_zuinteger.
> * command.h (typedef enum var_types): New enum
> 'var_zuinteger_unlimited'.
> Declare add_setshow_zuinteger_unlimited_cmd.
> * source.c (_initialize_source): Call add_setshow_zuinteger_unlimited_cmd.
Nit: The changelog entry for source.c should mention "listsize". And
the entry for do_setshow_command should also mention that it fixes the
setting of var_integer and var_zinteger to allow negative values.
Things are quite a mess, aren't they.
Adding yet another var_foo doesn't appeal to me, but we can't break
anything and being able to set both "0" and "unlimited" (expressed
however) would be nice.
Is there any real use-case that wants to be able to set negative
values and have "0" mean unlimited? It's never (until this patch)
been the case that one can set negative values to var_integer. Can we
remove (or at least deprecate) var_integer? [we'd switch all existing
uses to var_uinteger, the only remaining use would be the Python API]
btw, you also might want to update python/py-param.c.
Though py-param.c also doesn't handle var_zuinteger, and I don't mind
not extending the Python API until we know we want to.
next prev parent reply other threads:[~2012-08-02 8:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 12:52 [PATCH] Handle var_uinteger/var_zuinteger and case var_integer/var_zinteger together Yao Qi
2012-07-24 12:51 ` [committed]: " Yao Qi
2012-07-27 17:40 ` Khoo Yit Phang
2012-07-29 14:25 ` Yao Qi
2012-08-01 13:56 ` [RFC 0/3] New var_types var_zuinteger_unlimited Yao Qi
2012-08-01 13:56 ` [PATCH 1/3] var_zuinteger_unlimited and 'set listsize' Yao Qi
2012-08-01 16:14 ` Eli Zaretskii
2012-08-02 8:34 ` Doug Evans [this message]
2012-08-02 12:53 ` Yao Qi
2012-08-01 13:56 ` [PATCH 2/3] use zuinteger_unlimited for some remote commands Yao Qi
2012-08-01 13:56 ` [PATCH 3/3] use zuinteger_unlimited for heuristic-fence-post Yao Qi
2012-08-13 15:28 ` [RFC 0/3] Get rid of var_integer in CLI Yao Qi
2012-08-13 15:28 ` [PATCH 1/3] var_integer -> var_uinteger Yao Qi
2012-08-23 18:20 ` dje
2012-08-24 6:56 ` Yao Qi
2012-08-24 17:06 ` dje
2012-08-27 10:10 ` Yao Qi
2012-08-27 22:14 ` dje
2012-08-28 14:09 ` [committed]: " Yao Qi
2013-03-25 22:55 ` Change "set history size" back to signed (Re: [committed]: [PATCH 1/3] var_integer -> var_uinteger) Pedro Alves
2013-03-26 16:48 ` Yao Qi
2013-03-26 17:48 ` Pedro Alves
2013-03-27 8:54 ` Yao Qi
2013-03-27 17:34 ` Pedro Alves
2012-08-13 15:28 ` [PATCH 2/3] var_integer -> var_zuinteger_unlimited Yao Qi
2012-08-13 17:54 ` Eli Zaretskii
2012-09-14 18:12 ` Tom Tromey
2012-09-17 8:43 ` [committed]: " Yao Qi
2012-08-13 15:28 ` [PATCH 3/3] comments update Yao Qi
2012-09-14 18:13 ` Tom Tromey
2012-08-22 14:30 ` [ping] : [RFC 0/3] Get rid of var_integer in CLI Yao Qi
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=CADPb22QQeme8nTonPJ-TjgPQvC9WuzrJuiP0PHV_jbd1at7tLQ@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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