From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23027 invoked by alias); 1 Feb 2006 18:49:25 -0000 Received: (qmail 23019 invoked by uid 22791); 1 Feb 2006 18:49:25 -0000 X-Spam-Check-By: sourceware.org Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.195) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 01 Feb 2006 18:49:23 +0000 Received: by zproxy.gmail.com with SMTP id 8so205303nzo for ; Wed, 01 Feb 2006 10:49:22 -0800 (PST) Received: by 10.37.20.13 with SMTP id x13mr3416229nzi; Wed, 01 Feb 2006 10:49:22 -0800 (PST) Received: by 10.37.2.63 with HTTP; Wed, 1 Feb 2006 10:49:22 -0800 (PST) Message-ID: <8f2776cb0602011049u2479c5e5n7dec732b59927573@mail.gmail.com> Date: Wed, 01 Feb 2006 18:49:00 -0000 From: Jim Blandy To: Mark Kettenis Subject: Re: [RFC] Clean up var_integer/var_uinteger/var_zinteger mess Cc: gdb-patches@sourceware.org In-Reply-To: <200602011612.k11GCTK1017502@elgar.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200601311131.k0VBVjf8022306@jop31.nfra.nl> <8f2776cb0601312153s72d75a48ha6bc2fe75050d4fc@mail.gmail.com> <200602011612.k11GCTK1017502@elgar.sibelius.xs4all.nl> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-02/txt/msg00006.txt.bz2 On 2/1/06, Mark Kettenis 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. Then, of course, there's aix-thread.c which is using zinteger for a boolean.