CAR and CDR

In computer programming, car /kɑːr/ and cdr (/ˈkʌdər/ or /ˈkʊdər/) are primitive operations on cons cells (or "non-atomic S-expressions") introduced in the Lisp programming language. A cons cell is composed of two pointers; the car operation extracts the first pointer, and the cdr operation extracts the second.

Thus, the expression (car (cons x y)) evaluates to x, and (cdr (cons x y)) evaluates to y.

When cons cells are used to implement singly linked lists (rather than trees and other more complicated structures), the car operation returns the first element of the list, while cdr returns the rest of the list. For this reason, the operations are sometimes given the names first and rest or head and tail.

Etymology

Lisp was originally implemented on the IBM 704 computer, in the late 1950s.

The popular explanation that CAR and CDR stand for "Contents of the Address Register" and "Contents of the Decrement Register"[1] does not quite match the IBM 704 architecture; the IBM 704 does not have a programmer-accessible address register and the three address modification registers are called "index registers" by IBM.

The 704 and its successors has a 36-bit word length and a 15-bit address space. These computers had two instruction formats, one of which, the Type A, had a short, 3-bit, operation code prefix and two 15-bit fields separated by a 3-bit tag. The first 15-bit field was the operand address and the second held a decrement or count. The tag specified one of three index registers. Indexing was a subtractive process on the 704, hence the value to be loaded into an index register was called a "decrement".[2]:p. 8 The 704 hardware had special instructions for accessing the address and decrement fields in a word.[2]:p. 26 As a result it was efficient to use those two fields to store within a single word the two pointers needed for a list.[3]:Intro.

Thus, "CAR" is "Contents of the Address part of the Register". The term "register" in this context refers to "memory location".[4][5]

Precursors[6][7] to Lisp included functions:

each of which took a machine address as an argument, loaded the corresponding word from memory, and extracted the appropriate bits.

704 macros

The 704 assembler macro for cdr was:[8][9][10]

LXD JLOC,4  # C( Decrement of JLOC ) → C( IR4 )  # Loads the Decrement of location JLOC into IndexRegister 4
CLA 0,4     # C( 0 - C(IR4) ) → C( AC )          # The AC register receives the start address of the list
PDX 0,4     # C( Decrement of AC ) → C( IR4 )    # Loads the Decrement of AC into IndexRegister 4
PXD 0,4     # C( IR4 ) → C( Decrement of AC )    # Clears AC and loads IndexRegister 4 into the Decrement of AC

The 704 assembler macro for car was:[8][9][10]

LXD JLOC,4  # C( Decrement of JLOC ) → C( IR4 )  # Loads the Decrement of location JLOC into IndexRegister 4
CLA 0,4     # C( 0 - C(IR4) ) → C( AC )          # The AC register receives the start address of the list
PAX 0,4     # C( Address of AC ) → C( IR4 )      # Loads the Address of AC into IndexRegister 4
PXD 0,4     # C( IR4 ) → C( Decrement of AC )    # Clears AC and loads IndexRegister 4 into the Decrement of AC

A machine word could be reassembled by cons, which took four arguments (a,d,p,t).

The prefix and tag parts were dropped in the early stages of Lisp's design, leaving CAR, CDR, and a two-argument CONS.[3]

Compositions

Compositions of car and cdr can be given short and more or less pronounceable names of the same form. In Lisp, (cadr '(1 2 3)) is the equivalent of (car (cdr '(1 2 3))); its value is 2. Similarly, (caar '((1 2) (3 4))) is the same as (car (car '((1 2) (3 4)))); its value is 1. Most Lisps, for example Common Lisp and Scheme, systematically define all variations of two to four compositions of car and cdr.

Other computer languages

Many languages (particularly functional languages and languages influenced by the functional paradigm) use a singly linked list as a basic data structure, and provide primitives or functions similar to car and cdr. These are named variously first and rest, head and tail, etc. In Lisp, however, the cons cell is not used only to build linked lists but also to build pair and nested pair structures, i.e. the cdr of a cons cell need not be a list. In this case, most other languages provide different primitives as they typically distinguish pair structures from list structures either typefully or semantically. Particularly in typed languages, lists, pairs, and trees will all have different accessor functions with different type signatures: in Haskell, for example, car and cdr become fst and snd when dealing with a pair type. Exact analogues of car and cdr are thus rare in other languages.

References

  1. See, for example, Mitchell, John C. (2003), Concepts in Programming Languages, Cambridge University Press, pp. 2829, ISBN 9781139433488, Section 3.4, Innovations in the Design of Lisp. The reference identifies the IBM 704 and correctly explains the address and decrement part of a cons cell, but then it omits the "part of" in McCarthy's explanation.
  2. 1 2 704 - electronic data-processing machine http://bitsavers.informatik.uni-stuttgart.de/pdf/ibm/704/24-6661-2_704_Manual_1955.pdf
  3. 1 2 McCarthy, John (1979-02-12). "History of Lisp".
  4. McCarthy (1960, pp. 2627) discusses registers on the free list and in garbage collection.
  5. McCarthy, John; Abrahams, Paul W.; Edwards, Daniel J.; Hart, Timothy P.; Levin, Michael I. (1985), LISP 1.5 Programmer's Manual (second ed.), Cambridge, MA: MIT Press, ISBN 0-262-13011-4, page 36, describes cons cells as words with 15-bit "address" and "decrement" fields.
  6. A Fortran-Compiled List-Processing Language
  7. A Fortran-Compiled List-Processing Language; HTML transcription
  8. 1 2 Portions from NILS' LISP PAGES- http://t3x.dyndns.org/LISP/QA/carcdr.html
  9. 1 2 MIT AI Lab Memo 6 ftp://publications.ai.mit.edu/ai-publications/pdf/AIM-006.pdf
  10. 1 2 CODING for the MIT-IBM 704 COMPUTER ftp://bitsavers.informatik.uni-stuttgart.de/pdf/mit/computer_center/Coding_for_the_MIT-IBM_704_Computer_Oct57.pdf
Notes
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.