Re: Negative array indicies and slice()

Date	2012-11-01 09:15 -0700
From	Ethan Furman <ethan@stoneleaf.us>
Subject	Re: Negative array indicies and slice()
References	(2 earlier) <50912ADC.2020401@r3dsolutions.com> <CALwzid=_1TCQC5JryemVfVpBLWq=qZwy4hRjCPA5ha0vSm3=VA@mail.gmail.com> <50918716.3080305@r3dsolutions.com> <5092833F.4070609@stoneleaf.us> <CAPTjJmrUNjP-10_7tnt2LQP7HTSFqM8aNRBnxXi+v0U2XQVn_g@mail.gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.3156.1351787852.27098.python-list@python.org> (permalink)

Show all headers | View raw

Chris Angelico wrote:
> On Fri, Nov 2, 2012 at 1:12 AM, Ethan Furman <ethan@stoneleaf.us> wrote:
>> In other words, the slice contains the strings, and my code calculates
>> the offsets -- Python doesn't do it for me.
> 
> That's correct, but you're still translating those strings into
> numeric indices.

True, but the point is that the /slice/ contains a data type that is
neither a number, nor directly translatable into a number (that is, no
__index__ method), and my code would cease to function should that
change to slices be made.

~Ethan~

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Negative array indicies and slice() Ethan Furman <ethan@stoneleaf.us> - 2012-11-01 09:15 -0700

csiph-web