These are all real questions that I've faced while trying to write documentation. Let me make it clear that these are not rhetorical questions; I'm more interested in getting actual answers than arguing about using the code as the spec.
annotate is a general mechanism
ellipsize is supposed to display at most 80 characters of the input
median of an even-length list is supposed to return the lower of the middle two
cdar is supposed to be missing
(type 3.0) is supposed to be an int (for now)
support for complex numbers is supposed to be in Arc
client-ip is supposed to be there (for now)
afn stands for "anaphoric function"
rfn stands for "recursive function"
-----
> yes
Wasn't the point keeping the names car and cdr so you can compose them? (I remember reading such in one of pg's essays.) Then it seems to me to take full advantage of that you need to provide those names for use.
I don't think it is unreasonable to do the following, but it is currently not provided in Arc:
arc> (cdar '((1 2 3) (4 5 6))) Error: "reference to undefined identifier: _cdar"
Maybe this is just me missing CL's four levels of composition of car and cdr.
-----
On the one hand, it does feel like all the c....r s should be there.
On the other hand, I think cadr is pretty much the only one I ever actually use; and it is there.
-----
car --> hd
cdr --> tl
caar --> inner
cddr --> skip2
cadr --> second
-----