From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-75108-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 19287 invoked by alias); 23 Aug 2010 17:16:17 -0000
Received: (qmail 19278 invoked by uid 22791); 23 Aug 2010 17:16:17 -0000
X-SWARE-Spam-Status: No, hits=-0.7 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout21.012.net.il (HELO mtaout21.012.net.il) (80.179.55.169)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 23 Aug 2010 17:16:11 +0000
Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0L7M00D007X6A600@a-mtaout21.012.net.il> for gdb-patches@sourceware.org; Mon, 23 Aug 2010 20:16:07 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([77.126.37.231]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0L7M00CVL7YTZF90@a-mtaout21.012.net.il>; Mon, 23 Aug 2010 20:16:07 +0300 (IDT)
Date: Mon, 23 Aug 2010 17:16:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: RFA: fix PR python/11915
In-reply-to: <m3iq31qn19.fsf@fleche.redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83fwy5nt7w.fsf@gnu.org>
References: <m3y6c0yky1.fsf@fleche.redhat.com> <83eidspff4.fsf@gnu.org> <m3iq31qn19.fsf@fleche.redhat.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2010-08/txt/msg00390.txt.bz2

> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Mon, 23 Aug 2010 11:03:30 -0600
> 
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> 
> Eli> "Inclusive upper bound"?  Does this mean that if the argument is N,
> Eli> then the array will have N+1 members, from zero to N?  That sounds
> Eli> against the intuition, doesn't it?
> 
> Yes, but it is the only way to allow an array whose upper bound is
> MAXINT.  I think it is also consistent with Type.range.

It means I'd need to use an argument of zero to have an array of one
element.  It also means the size of an array whose upper bound is
MAXINT is MAXINT+1, which could overflow, no?

I'm fine with this if users will be, but it feels strange.

> >> +given, the first argument is the lower bound of the array, and the
> >> +second argument is the upper bound of the array.
> 
> Eli> Will the reader know whether negative arguments are allowed (provided
> Eli> that the second is greater than the first)?  Or is it a good idea to
> Eli> tell explicitly?
> 
> I added a note.  New patch appended.

Thanks, this version is fine with me.