From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-75099-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 21753 invoked by alias); 21 Aug 2010 07:54:50 -0000
Received: (qmail 21741 invoked by uid 22791); 21 Aug 2010 07:54:49 -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 mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 21 Aug 2010 07:54:42 +0000
Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0L7H00J00SISKT00@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Sat, 21 Aug 2010 10:54:29 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([77.127.220.100]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0L7H00JNOSMS2360@a-mtaout22.012.net.il>; Sat, 21 Aug 2010 10:54:29 +0300 (IDT)
Date: Sat, 21 Aug 2010 07:54:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: RFA: fix PR python/11915
In-reply-to: <m3y6c0yky1.fsf@fleche.redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83eidspff4.fsf@gnu.org>
References: <m3y6c0yky1.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/msg00381.txt.bz2

> From: Tom Tromey <tromey@redhat.com>
> Date: Fri, 20 Aug 2010 16:32:22 -0600
> 
> This patch fixes PR python/11915.
> 
> It adds a new method, Type.array, so that users can create new array
> types at runtime.

Thanks.

> +@defmethod Type array @var{n1} @r{[}@var{n2}@r{]}
> +Return a new @code{gdb.Type} object which represents an array of this
> +type.  If one argument is given, it is the inclusive upper bound of
> +the array; in this case the lower bound is zero.  If two arguments are

"Inclusive upper bound"?  Does this mean that if the argument is N,
then the array will have N+1 members, from zero to N?  That sounds
against the intuition, doesn't it?

> +given, the first argument is the lower bound of the array, and the
> +second argument is the upper bound of the array.

Will the reader know whether negative arguments are allowed (provided
that the second is greater than the first)?  Or is it a good idea to
tell explicitly?