3 ms·
It all started with your lists. I think that was when I really fell in love. You see in a language like Java or php if you want to get the last element of the l
by stcredzero 17y ago
It all started with your lists. I think that was when I really fell in love. You see in a language like Java or php if you want to get the last element of the list you have to write something like $a[count($a) - 1]. But python was different: just write a[-1].
Don't take this as hostile. Rather as an observation of the shifted expectations of programmer subculture.
So a cryptic negative index counts as "elegant?" Wouldn't it be more straightforward just to ask a list for "last?"
Here's the equivalent Smalltalk:
list last
In Ruby:
list.1ast
Laypeople would have an immediate inkling of either. The negative array index stuff would cause at least some python prompt exploration or the shift to some sort of reference.
- viraptor 17y agoThat's clear and elegant for the last element. But now you need another function for [-2].
- llimllib 17y agoMaybe by analogy to cddr, ruby should have laast?
- mnemonik 17y agoBut then you are throwing all the readability gains of list.last vs. list[-1] right out the window and we are back to square one. I don't think anyone finds Lisp's car and cdr (much less cadr and friends) particularly intuitive when they are first introduced to whichever dialect it happens to be. You get used to it, and when needed, write specific-case functions for readability that are simple wrappers to those combo functions. Which I think is probably best no matter whether you have last or [-1], this argument is kind of pointless. Step back and think about why you need that item, write a small wrapper function to grab that it and name the wrapper well so it provides a little semantic context to whoever ends up reading the code later.
- llimllib 17y ago> But then you are throwing all the readability gains of list.last vs. list[-1] right out the window and we are back to square one. ermmm, I apparently forgot to add the <sarcasm> tag.
- jamesbritt 17y agoSo ... what? Don't have clear, intuitive methods for common cases? Ruby also provides arr[-1], arr[-2], etc. But there's a subtle difference when I read arr.last vs. arr[-1].
- codexon 17y agoThe first index is 0, the next is 1, and if you loop around backwards, it's -1. Makes sense to me.
- stcredzero 17y agoThat's another demonstration of my point. Many, many people out there in the non-tech world would expect that the first element would have an index of "1". First = "1st" = "#1." On the other hand, we often experience the convenience of pointer arithmetic (or similar) with zero-indexed arrays. Yet another programmer/techy and ordinary person divide.
- codexon 17y agoIf you want something for non-techies, you pick something like Applescript. 0-based indexing is noob friendly because most cs algorithms use it so you can do a straightforward translation. Would it be better to go with 1-based and make this harder for novice programmers? I don't think so.
- jamesbritt 17y ago"Makes sense to me." Me too. But: when I see code that refers to first and last, I expect that the first and last elements are special. When I see integers, it leads me to think that all of the elements are about equally important. I also find it easier to read the text form rather than the integers; I don't have to look carefully to see if it's 1, 11, 7; code reading goes more smoothly. Having both forms allows me to express, and parse, intention better.