From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jimb@red-bean.com
Cc: mark.kettenis@xs4all.nl, gdb-patches@sourceware.org
Subject: Re: [RFC] Clean up var_integer/var_uinteger/var_zinteger mess
Date: Wed, 01 Feb 2006 19:24:00 -0000 [thread overview]
Message-ID: <200602011923.k11JNn7Q024255@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <8f2776cb0602011049u2479c5e5n7dec732b59927573@mail.gmail.com> (message from Jim Blandy on Wed, 1 Feb 2006 10:49:22 -0800)
> X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on
> elgar.sibelius.xs4all.nl
> X-Spam-Level:
> X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=no
> version=3.1.0
> DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
> s=beta; d=gmail.com;
> h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
> b=TFTIQB+EK02V1vfXwI4QJr/gwBrh3UD5JTREmxEUO/A7bevYVtY02UcXlTjdbxMdWVK0UFIL+7lGFhq9OI4I4ZDiTkjxogv8dHMT4YB0XjPaJwFosrXjv5aSAOTv7blG57qzR2FfqT+q/8wjS018LVkizr+i29iXHZipUDHhXDc=
> Date: Wed, 1 Feb 2006 10:49:22 -0800
> From: Jim Blandy <jimb@red-bean.com>
> Sender: jimblandy@gmail.com
> Cc: gdb-patches@sourceware.org
> Content-Disposition: inline
> X-XS4ALL-DNSBL-Checked: mxdrop24.xs4all.nl checked 64.233.162.193 against DNS blacklists
> X-Virus-Scanned: by XS4ALL Virus Scanner
> X-XS4ALL-Spam-Score: 0 ()
> X-XS4ALL-Spam: NO
> Envelope-To: mark.kettenis@xs4all.nl
> X-MIME-Autoconverted: from quoted-printable to 8bit by mxdrop24.xs4all.nl id k11InHwe077021
> X-UIDL: 1138819766._smtp.mxdrop24.77065,S=2619
>
> On 2/1/06, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
> > Actually, it'd make sense if the existing
> > var_integer/var_uinteger/var_zinteger would accept "unlimited".
> > That'd make your var_limit unnecessary.
> >
> > Does anyone see any problems with that?
>
> Well, I presume that sometimes (often) those are used for limits of
> something, and sometimes they're genuine integers. Surely there's
> something in GDB where a negative value would make sense. I don't
> like the idea of accepting "unlimited" for a quantity that isn't a
> limit on anything.
Well, the current code already prints "unlimited" for
var_integer/var_uinteger. I'd say it is only logical that they can be
set to "unlimited" too.
Guess your var_zinteger is your "genuine" integer; we probably
shouldn't accept "unlimited" for those.
> Then, of course, there's aix-thread.c which is using zinteger for a boolean.
Of course. That's the proper type for boolean expressions ;-).
Mark
next prev parent reply other threads:[~2006-02-01 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 11:32 Mark Kettenis
2006-02-01 5:53 ` Jim Blandy
2006-02-01 16:13 ` Mark Kettenis
2006-02-01 18:49 ` Jim Blandy
2006-02-01 19:24 ` Mark Kettenis [this message]
2006-02-01 19:28 ` Jim Blandy
2006-02-01 21:17 ` Daniel Jacobowitz
2006-02-02 0:11 ` Joel Brobecker
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=200602011923.k11JNn7Q024255@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=jimb@red-bean.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