Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/2] use zuinteger_unlimited for some remote commands
Date: Wed, 06 Mar 2013 00:30:00 -0000	[thread overview]
Message-ID: <CADPb22RfcWmPt_eOamStQuvPWn_HePrZ-+ihAKQvRnNRpskRDg@mail.gmail.com> (raw)
In-Reply-To: <5136341A.4050605@redhat.com>

I think we need to take the set of var_foo options, and choose
something that works on the whole.

var_uinteger has values [1,UINT_MAX-1] plus 0 mapping to UINT_MAX.
var_zuinteger has values [0,UINT_MAX].
And I don't see a plan to change those to int.

Fortunately, I don't see var_zuinteger_unlimited in py-param.c.
What if we rename it to var_zpinteger_unlimited or some such.
[p for positive]
[I'd still keep it out of the python API until there's a compelling
need for it.]


  reply	other threads:[~2013-03-06  0:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 13:29 [PATCH 0/2] Use zuinteger_unlimited Yao Qi
2013-02-15 13:29 ` [PATCH 1/2] use zuinteger_unlimited for some remote commands Yao Qi
2013-03-04 13:19   ` Pedro Alves
2013-03-04 14:38     ` Yao Qi
2013-03-04 16:21       ` Pedro Alves
2013-03-05  7:45         ` Yao Qi
2013-03-05 12:59           ` Pedro Alves
2013-03-05 17:33             ` Doug Evans
2013-03-05 18:07               ` Pedro Alves
2013-03-06  0:30                 ` Doug Evans [this message]
2013-02-15 13:29 ` [PATCH 2/2] use zuinteger_unlimited for heuristic-fence-post Yao Qi
2013-02-25  3:15 ` ping : [PATCH 0/2] Use zuinteger_unlimited 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=CADPb22RfcWmPt_eOamStQuvPWn_HePrZ-+ihAKQvRnNRpskRDg@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --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