From: arnold@skeeve.com (arnold@skeeve.com)
Subject: [TUHS] Array index history
Date: Wed, 07 Jun 2017 07:20:43 -0600 [thread overview]
Message-ID: <201706071320.v57DKhmJ026303@freefriends.org> (raw)
In-Reply-To: <CAH_OBifFdBTOD6xXAhWE61GbvmF_TQ5HBHhUU-SFx=AXn1=J+Q@mail.gmail.com>
shawn wilson <ag4ve.us at gmail.com> wrote:
> I learned the other day that array indexes in some languages start at 1
> instead of 0. This seems to be an old trend that changed around the 70s?
> Who started this? Why was the change made?
>
> It seems to have come about around the same time as C, but interestingly
> enough Lua is kinda in between (you can start an array at 0 or 1).
> Smalltalk can probably have a 0 base index just by it's nature, but I
> wonder whether that would work in a 40 year old interpreter.
Basically, until C came along, the standard practice was for indices
to start at 1. Certainly Fortran and Pascal did it that way. I suspect
that all the Algol family languages did too, but I only did a little
Algol W programming in colledge and that was long ago. I think Cobol also.
Pascal (IIRC) allowed you to specify upper and lower bounds, something
like
foo : array[5..10] of integer;
with runtime bounds checking on array accesses. (I could be wrong ---
it's been a LLLLOOONNNGGG time.)
HTH,
Arnold
next prev parent reply other threads:[~2017-06-07 13:20 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH_OBiewwwS6kbdWKUO-j3v=Do+Y9AzBn4ZkyVic7LOJN5WX7w@mail.gmail.com>
[not found] ` <CAH_OBid5q-YeB6UYeOfjW68s3nb3TX_icC5dFMapfo=7_q5DUQ@mail.gmail.com>
[not found] ` <CAH_OBideJeNGiiys=VOEYcU1cffSg+6zDOD39HOU74vumQF0kA@mail.gmail.com>
[not found] ` <CAH_OBie_+dQXOC2OaZii5K=j1Ljmv-OvAVXvyypoLJ10jaysWA@mail.gmail.com>
[not found] ` <CAH_OBidXd1Lpgp8ttM3sWLfXDT0ms5EGAzEjPH9QkY+bXyev2w@mail.gmail.com>
[not found] ` <CAH_OBifge2RrwcDvSV46gwLAc0wHVtH++gdMBhXi-x8C0a_2jw@mail.gmail.com>
[not found] ` <CAH_OBic3MTy-20C_T2ciT2x+EjNZvXR2PJ0OzB0qRp1gd2OL-g@mail.gmail.com>
2017-06-07 12:56 ` shawn wilson
2017-06-07 13:16 ` Ron Natalie
2017-06-07 13:20 ` arnold [this message]
2017-06-07 13:50 ` Michael Kjörling
2017-06-07 14:02 ` arnold
2017-06-08 11:28 ` Christian Neukirchen
2017-06-08 14:56 ` shawn wilson
2017-06-07 14:58 ` Tony Finch
2017-06-07 23:57 ` Dave Horsfall
2017-06-07 16:31 ` Lyndon Nerenberg
2017-06-08 0:47 ` Bakul Shah
2017-06-07 17:59 ` Tim Bradshaw
2017-06-07 18:29 ` Clem Cole
2017-06-07 18:46 ` Arthur Krewat
2017-06-07 19:03 ` Ron Natalie
2017-06-07 19:15 ` Arthur Krewat
2017-06-07 19:49 ` Ron Natalie
2017-06-08 1:58 ` ARJANEN Loïc Jean David
2017-06-08 13:49 ` Random832
2017-06-08 13:55 ` Arthur Krewat
2017-06-08 18:41 ` Tim Bradshaw
2017-06-08 2:45 ` Robert Swierczek
2017-06-08 4:05 ` Dave Horsfall
2017-06-08 6:19 ` Peter Jeremy
2017-06-08 7:02 ` Dave Horsfall
2017-06-08 13:53 ` Ron Natalie
2017-06-08 2:27 Doug McIlroy
2017-06-08 12:49 ` William Cheswick
2017-06-08 12:56 ` Michael Kjörling
2017-06-08 13:45 ` Dan Cross
2017-06-08 13:57 ` Ron Natalie
2017-06-10 21:08 ` Nemo
2017-06-08 15:04 ` Dave Horsfall
2017-06-08 15:09 ` William Pechter
2017-06-08 16:53 ` Steve Nickolas
2017-06-08 20:17 ` Larry McVoy
2017-06-09 0:03 ` Greg 'groggy' Lehey
2017-06-08 9:16 Richard Tobin
[not found] <mailman.882.1496854900.3779.tuhs@minnie.tuhs.org>
2017-06-08 18:20 ` David
2017-06-08 18:55 ` Ron Natalie
2017-06-09 21:21 ` Steve Johnson
2017-06-09 21:52 ` Arthur Krewat
2017-06-08 22:29 ` Johnny Billquist
2017-06-08 23:16 ` Ron Natalie
2017-06-08 23:41 ` Steve Nickolas
2017-06-09 15:12 ` Random832
2017-06-09 16:30 ` Ron Natalie
2017-06-09 0:21 ` Johnny Billquist
2017-06-09 0:25 ` Pete Turnbull
2017-06-09 1:19 ` Toby Thain
2017-06-09 2:14 ` Pete Turnbull
[not found] <mailman.890.1496953026.3779.tuhs@minnie.tuhs.org>
2017-06-08 22:28 ` Johnny Billquist
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=201706071320.v57DKhmJ026303@freefriends.org \
--to=arnold@skeeve.com \
/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 NNTP newsgroup(s).