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.
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?
I don't think either one creates more off-by-one errors in people used to it.
Also, believe it or not, on various machines and OS's it's legal to map address 0.
Edit: Your edit makes even less sense. There is no such thing as a "null index", much less an operation to "access a null index".