This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Python: should gdb.Value array indexing check bounds?

From: Matt Rice <ratmice at gmail dot com>
To: Paul_Koning at dell dot com
Cc: gdb at sourceware dot org
Date: Tue, 20 Sep 2011 09:12:06 -0700
Subject: Re: Python: should gdb.Value array indexing check bounds?
References: <09787EF419216C41A903FD14EE5506DD03094C6D5D@AUSX7MCPC103.AMER.DELL.COM>

On Tue, Sep 20, 2011 at 9:04 AM,  <Paul_Koning@dell.com> wrote:
> Currently, if a gdb.Value object corresponds to an array, array indexing is done C-style: no bounds checking, just pointer arithmetic.? That's somewhat unnatural to Python.? Should it do a range check instead, and raise IndexError for out of range index values?
>
> That wouldn't affect indexing of pointers, since those don't have a range so the only possible approach is the C one.

I'd think no because of things like:
http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Zero-Length.html
(which is possible with non-zero length arrays also).

References:
- Python: should gdb.Value array indexing check bounds?
  - From: Paul_Koning

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]