From: <Paul_Koning@Dell.com>
To: <gdb@sourceware.org>
Subject: Python: should gdb.Value array indexing check bounds?
Date: Tue, 20 Sep 2011 16:05:00 -0000 [thread overview]
Message-ID: <09787EF419216C41A903FD14EE5506DD03094C6D5D@AUSX7MCPC103.AMER.DELL.COM> (raw)
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.
paul
next reply other threads:[~2011-09-20 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 16:05 Paul_Koning [this message]
2011-09-20 16:12 ` Matt Rice
[not found] ` <09787EF419216C41A903FD14EE5506DD03094C6D7D@AUSX7MCPC103.AMER.DELL.COM>
2011-09-20 16:19 ` Paul Koning
2011-10-05 18:08 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09787EF419216C41A903FD14EE5506DD03094C6D5D@AUSX7MCPC103.AMER.DELL.COM \
--to=paul_koning@dell.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox