public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pmuldoon at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/13339] type.array(X) creates array of X+1 items
Date: Thu, 27 Oct 2011 12:52:00 -0000	[thread overview]
Message-ID: <bug-13339-4717-fjusnXKgpM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13339-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13339

--- Comment #4 from Phil Muldoon <pmuldoon at redhat dot com> 2011-10-27 12:51:40 UTC ---
I've really no problem with a single argument being "length", in fact it makes
sense.  But this would break an established and documented API.  If a
maintainer waives that, that is fine, I will change it.  There is an argument
to be made that this was a bug, and we fixed it (and this would be ok under our
API promise), but we already documented the fact that the lower-bound would be
assumed to be zero in the case of single-argument specifications.  We could add
a "length=" keyword which the user could pass in-place of arguments - that
would account for the specification being a length, not a range.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2011-10-27 12:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24 21:58 [Bug python/13339] New: " jan.kratochvil at redhat dot com
2011-10-27 10:58 ` [Bug python/13339] " pmuldoon at redhat dot com
2011-10-27 12:04 ` pmuldoon at redhat dot com
2011-10-27 12:38 ` jan.kratochvil at redhat dot com
2011-10-27 12:52 ` pmuldoon at redhat dot com [this message]
2011-10-27 13:46 ` jan.kratochvil at redhat dot com
2011-11-02 16:27 ` tromey at redhat dot com
2011-11-02 16:30 ` jan.kratochvil at redhat dot com
2011-12-02  0:33 ` dje at google dot com
2011-12-02 18:51 ` tromey at redhat dot com
2012-01-09  9:37 ` jan.kratochvil at redhat dot com

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=bug-13339-4717-fjusnXKgpM@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).