3 ms·
True enough, but that causes much less damage because except in the rarest situations, you never write code to do random access to an array of children, you jus
by ajross 10y ago
True enough, but that causes much less damage because except in the rarest situations, you never write code to do random access to an array of children, you just iterate over them without using indices at all.
This is opening up a situation where you have a 2D Javascript array for a model and a bunch of components in the layout (a chessboard, imagine). And the coordinates won' t match!
- torrent-of-ions 10y agoWhat is your concern? Code beauty? What kind of programmer can't deal with converting between 0 and 1 based arrays?
- Risord 10y agoIts easy for sure but I think you agree that we don't want random multipliers or string prefixes to array idexes just for fun.
- ajross 10y agoWhat kind of programmer can't remember to check return values of system calls? What kind of programmer can't deal with properly escaping input under the control of the user? What kind of programmer can't deal with keeping array indexes in bounds? (tl;dr: you. And me.)
- torrent-of-ions 10y agoNone of that is like dealing with 0/1 arrays. Almost everything you encounter in real life starts with 1, not 0. If anything it's the 0 based array that should be consider "wrong" and the cause of so many errors. But we use 0 based arrays because of the C/assembly legacy where the 0 means the location of the array with a 0 offset.
- garaetjjte 10y agohttp://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/EWD831.html http://www.cs.utexas.edu/users/EWD/transcriptions/EWD08xx/EW...
- kenshi 10y agoWhat kind of programmer hasn't learnt from and embraced the fact that programmers are human and that humans make mistakes?