News for hackers. Stuff that matters.
Re:The origin of zero-based array indexing by ronaldx on Tuesday December 10, 2013 @07:07AM (#6880224)
In my opinion, one-indexing is better:

* Ordinal and cardinal numbers both start from 1 in all major human languages

* Humans didn't use the number zero until relatively recently in mathematical history - this illustrates that it's intuitively hard for humans to grasp.

* It's important to separate the cases of 0 and null, which is easier if you use 1-indexing. This has got to save a lot of tricky bugs.

High-level programming languages are designed for humans. Humans 1-index everything, so these would be better 1-indexed.

Low-level programming languages are designed for computers. You can 0-index there, for the reasons that you stated.

As programmers, we had to explicitly learn 0-indexing. 0-indexing creates an artificial barrier to enter programming, when there are so many other barriers that we should be trying to relieve.

Re:The origin of zero-based array indexing by cliffbean on Tuesday December 10, 2013 @07:48AM (#6880389)
It's true that humans hadn't discovered zero until relatively recently in mathematical history. Should we reject these "new" developments in numeracy, and go back to roman numerals? One could make a pretty strong case that roman numerals are more intuitive, more human.
Re:The origin of zero-based array indexing by ronaldx on Tuesday December 10, 2013 @08:14AM (#6880499)
I take your point here - but no developments in numeracy include counting objects from zero.
Re:The origin of zero-based array indexing by lukeschlather on Tuesday December 10, 2013 @10:01AM (#6881039)
That's because making the switch from 1-indexing to 0-indexing is extremely counter-intuitive. However, take a hypothetical person who learned 0-indexing socially from birth, I'd imagine they'd be just as confused by 1-indexing.
Re:The origin of zero-based array indexing by pubby on Tuesday December 10, 2013 @09:32AM (#6880884)
When you use a count variable in programming, do you initialize it to 1?
Re:The origin of zero-based array indexing by ronaldx on Tuesday December 10, 2013 @09:46AM (#6880959)
Making this argument agrees with my general point: that high-level programming languages ought to count as humans do.
Re:The origin of zero-based array indexing by pubby on Tuesday December 10, 2013 @09:57AM (#6881021)
My point was that it's rather awkward to count from 1 when doing programming.

For instance, could you rewrite this function where int count = 1; and have it still be intuitive?

  int count_occurrences(std::vector<int> vec, int value) {
    int count = 0;
    for(int i = 0; i != vec.size(); ++i) { // using 0-based index
      if(vec[i] == value)
        ++count;
    }
    return count;
  }
My attempt is: (look how ugly!)

  int count_occurrences(std::vector<int> vec, int value) {
    if(vec.empty())
      return 0;
    count = 1;
    for(int i = 2; i <= vec.size(); ++i) { // using 1-based index
      if(vec[i] == value)
        ++count;
    }
    return count;
  }
Re:The origin of zero-based array indexing by tg3 on Tuesday December 10, 2013 @09:33PM (#6885509)
As another commenter pointed out, it's only the indices that are one-based. I think it would look something like this:

  int count_occurrences(std::vector<int> vec, int value) {
    int count = 0;
    for(int i = 1; i <= vec.size(); ++i) { // using 1-based index
      if(vec[i] == value)
        ++count;
    }
    return count;
  }
Off the top of my head, this has a number of benefits in higher level languages. For instance in Javascript, here are some common inconveniences caused by zero-based indices:

  var lastEl = arr[arr.length - 1];

  if(arr.indexOf(someEl) !== -1) {
    // do something knowing that someEl is in the array
  }
and if we lived in a one-based world, here's what they would look like:

  var lastEl = arr[arr.length];

  if(arr.indexOf(someEl)) {
    // do something knowing that someEl is in the array
  }
Re:The origin of zero-based array indexing by zenojevski on Tuesday December 10, 2013 @10:40AM (#6881289)
It's only `i` (the index) that's meant to begin from 1.

`count` is a quantity, not an index, and there are such things as "zero apples". But you start counting them from the first one.

Re:The origin of zero-based array indexing by cliffbean on Tuesday December 10, 2013 @09:38AM (#6880921)
I agree that it's not at the same level, but there certainly are developments.
Re:The origin of zero-based array indexing by mtdewcmu on Tuesday December 10, 2013 @01:23PM (#6882527)
Computers aren't a development in numeracy?
Re:The origin of zero-based array indexing by moron4hire on Tuesday December 10, 2013 @08:27AM (#6880548)
point 1 is tautological. point 2 is incorrect. point 3 is a problem of the concept of null being a mistake, not of 0-indexed arrays.

programming is math, and all the math works better if 0-index arrays. Leave programming language design to the adults.

Re:The origin of zero-based array indexing by mtdewcmu on Tuesday December 10, 2013 @12:50PM (#6882254)
1-indexing is no longer intuitive when numbers become large. Years are 1-indexed; how many people observed the start of the millenium in 2001?
Re:The origin of zero-based array indexing by dllthomas on Tuesday December 10, 2013 @12:01PM (#6881842)
You don't index pointers by pointers, so I don't see point 3. Your types distinguish zero from null.