Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Eli Zaretskii <eliz@gnu.org>,  gdb-patches@sourceware.org
Subject: Re: [RFA] Handle var_zuinteger and var_zuinteger_unlimited from Python
Date: Wed, 02 May 2018 16:06:00 -0000	[thread overview]
Message-ID: <87sh7a59f9.fsf@tromey.com> (raw)
In-Reply-To: <871seu6o81.fsf@tromey.com> (Tom Tromey's message of "Wed, 02 May	2018 10:01:34 -0600")

Eli> This part is approved, but it sounds like only 1 of the 3 differences
Eli> from PARAM_ZUINTEGER should actually be mentioned, as the other 2 --
Eli> that 0 is interpreted as itself and negative values are generally not
Eli> allowed -- are already present in PARAM_ZUINTEGER.  Or did I miss
Eli> something?

Tom> No, you didn't, that seems correct to me.
Tom> Also the value is actually signed.

Tom> I've changed it to:

Tom>     The value is an signed integer.  This is like @code{PARAM_ZUINTEGER},
Tom>     except the special value -1 should be interpreted to mean
Tom>     ``unlimited''.  Other negative values are not allowed.

So what I actually wrote and what you wrote that I agreed with are not
the same: I left in the text about other negative values.  I thought
this still made sense given that the value is actually signed, but let
me know which way you'd prefer.

thanks,
Tom


  reply	other threads:[~2018-05-02 16:06 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
2018-05-02 16:01   ` Tom Tromey
2018-05-02 16:06     ` Tom Tromey [this message]
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=87sh7a59f9.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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