News for hackers. Stuff that matters.
Re:Why Python uses 0-based indexing. It's because of slices by Dylan16807 on Wednesday October 23, 2013 @10:52PM (#6603150)
>There is no such thing as a "null index",

Would you rather I write "index that is 0 in a world where indexes start at 1" over and over? I am willing to do that if it helps make the conversation smoother.

>much less an operation to "access a null index".

foo_array[0]; //operation to do an access with a null index

>Also, believe it or not, on various machines and OS's it's legal to map address 0.

Which is a bad thing. You get a couple extra variable slots in exchange for thousands of privilege-escalation bugs that could instead be crash bugs.

Re:Why Python uses 0-based indexing. It's because of slices by lectrick on Wednesday October 23, 2013 @11:51PM (#6603319)
How in the hell does "accidentally" accessing the first element of an array (by "accidentally" passing 0 to an array in a language that has 0-based indexing) result in "privilege escalation errors"? That's just "shitty programming".

For that matter, how does a 1-based indexing language NOT result in far more "off by one" errors which would include the kind of errors commonly known as "buffer overflow" errors?

Re:Why Python uses 0-based indexing. It's because of slices by Dylan16807 on Thursday October 24, 2013 @01:45AM (#6603577)
In most cases indexing doesn't affect safety, the privilege stuff was related to what eridius was talking about with physical addresses.

I don't think either one creates more off-by-one errors in people used to it.