This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFA: fix PR python/11915
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sat, 21 Aug 2010 10:56:31 +0300
- Subject: Re: RFA: fix PR python/11915
- References: <m3y6c0yky1.fsf@fleche.redhat.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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?