1. <operating system> A record of previous user inputs (e.g. to
	a {command interpreter}) which can be re-entered without
	re-typing them.  The major improvement of the {C shell} (csh)
	over the {Bourne shell} (sh) was the addition of a command
	history.  This was still inferior to the history mechanism on
	{VMS} which allowed you to recall previous commands as the
	current input line.  You could then edit the command using
	cursor motion, insert and delete.  These sort of history
	editing facilities are available under {tcsh} and {GNU Emacs}.

	2. <history> {The history of computing
	(http://ei.cs.vt.edu/~history/index.html)}.

	3. See {Usenet} newsgroups {news:soc.history} and
	{news:alt.history} for discussion of the history of the world.

	(1995-04-05)

In {object-oriented programming} sending a message to an
	{object} (to invoke a {method}) is equivalent to calling a
	{procedure} in traditional programming languages, except that
	the actual code executed may only be selected at run time
	depending on the {class} of the object.  Thus, in response to
	the message "drawSelf", the method code invoked would be
	different if the target object were a circle or a square.

	(1995-02-16)

<data> A data structure holding many values, possibly of
	different types, which is usually accessed sequentially,
	working from the head to the end of the tail - an "ordered
	list".  This contrasts with a (one-dimensional) {array}, any
	element of which can be accessed equally quickly.

	Lists are often stored using a cell and pointer arrangement
	where each value is stored in a cell along with an associated
	pointer to the next cell.  A special pointer, e.g. zero, marks
	the end of the list.  This is known as a (singly) "linked
	list".  A doubly linked list has pointers from each cell to
	both next and previous cells.

	An unordered list is a {set}.

	(1998-11-12)

1. <file format> A single file containing one or (usually)
	more separate files plus information to allow them to be
	extracted (separated) by a suitable program.

	Archives are usually created for software distribution or
	{backup}.  {tar} is a common format for {Unix} archives, and
	{arc} or {PKZIP} for {MS-DOS} and {Microsoft Windows}.

	2. <operating system> To transfer files to slower, cheaper
	media (usually {magnetic tape}) to free the {hard disk} space
	they occupied.  This is now normally done for long-term
	storage but in the 1960s, when disk was much more expensive,
	files were often shuffled regularly between disk and tape.

	3. <networking> {archive site}.

	(1996-12-08)