News for hackers. Stuff that matters.
Re:The Origin of CAR and CDR in Lisp (2005) by kruhft on Monday December 26, 2016 @12:51PM (#13259056)
car and cdr may not be the best names, but they allowed for composition, like:

    (caar x) == (car (car x))
    (cddar x) == (cdr (cdr (car (x)))
Something which you can't do with first and rest. This has (AFAIK) always been one of the arguments for car and cdr.
Re:The Origin of CAR and CDR in Lisp (2005) by s_kilk on Monday December 26, 2016 @01:58PM (#13259313)
I dunno, as a latecomer lisp-enthusiast, that cadaddaaadr stuff seems heinous to me.
Re:The Origin of CAR and CDR in Lisp (2005) by kazinator on Monday December 26, 2016 @02:29PM (#13259425)
I've grown to like it, and implemented it in TXR Lisp one level deeper than CL, all the way to cddddr.

http://www.nongnu.org/txr/txr-manpage.html#N-03E5CED9

The code for them is generated textually: http://www.kylheku.com/cgit/txr/tree/gencadr.txr

Re:The Origin of CAR and CDR in Lisp (2005) by kruhft on Monday December 26, 2016 @09:44PM (#13260951)
It's not pretty, but it has a consistency to it that includes a lot of compact information in a digestable manner. It takes no longer to decode what the instructions say, but it saves a lot of time parsing, for the human reader of the program.

Compare:

    (caadar x) => (car (car (car (cdr (car x)))))
Saves parens too.
Re:The Origin of CAR and CDR in Lisp (2005) by kbp on Monday December 26, 2016 @11:53PM (#13261343)
You can make it even easier on human readers by defining accessors (even if they're just wrappers over car/cdr) and giving them meaningful names. Asking for the car of the car of the cdr of the car of an ad-hoc data structure is pretty hostile toward human readers regardless of whether or not you use caadar.
Re:The Origin of CAR and CDR in Lisp (2005) by junke on Tuesday December 27, 2016 @02:55AM (#13261890)
That's why you actually won't find many instances of such patterns in practice. Either you refactor to have structures/classes, or you define your own accessors. Besides, if you are using CL, FIRST, SECOND, THIRD, ... , TENTH, NTH and REST are defined by the spec (http://clhs.lisp.se/Body/f_firstc.htm).
Re:The Origin of CAR and CDR in Lisp (2005) by hinkley on Tuesday December 27, 2016 @12:15AM (#13261416)
Are you kidding? cdar would be the second element, cddar the third, and so on. And they're harder to misread on a scan through the code.

As a general rule, I assume that I read most lines of the code not when I'm writing it, nor fixing a bug, but while I'm trying to locate a bug of unknown location. The complexity or trickiness of a function that you are actively modifying can be pretty high and you'll still grasp it. But a function not even involved with a problem needs to be even more legible if you don't want to repeatedly waste time contemplating it to determine if you should move on.

Re:The Origin of CAR and CDR in Lisp (2005) by junke on Tuesday December 27, 2016 @02:51AM (#13261868)
Keep calm and read the Common Lisp specification (http://clhs.lisp.se/Body/f_firstc.htm)

There are first, etc... accessors (other Lisps might define them too, it is so easy to implement). People are encouraged to use them, especially for lists, and are even encouraged to not use them but prefer objects with named slots.

The general advice is to reserve C..R functions for trees, but this is actually rarely needed, especially when using pattern matching.

Re:The Origin of CAR and CDR in Lisp (2005) by lisper on Monday December 26, 2016 @05:00PM (#13260008)
I've always like FST and RST (FirST and ReST) because they're more mnemonic but they still compose like CAR and CDR (e.g. FFRRFST == CAADDAR).
Re:The Origin of CAR and CDR in Lisp (2005) by kruhft on Monday December 26, 2016 @09:42PM (#13260946)
Good point. Haven't seen that example before.