things not to forget to put in docs:

lxlist stuff:
    the (per list item type) `copy' method receives as 3rd argument the address
	at which the item value will be stored.  this address may be recorded,
	for it will be preserved by the lxlist code.

-------------------------------------------------------------------------------

reference function arguments are not retained.  and this is okay, as long as
    only variables are allowed for such arguments.

-------------------------------------------------------------------------------

aime.5:

    make object a language feature (actually, an e4 type)

-------------------------------------------------------------------------------

aime, the 2nd:

    (not that there is any planned second revision of aime, but if it would be
     it should include these)

    eliminate the pointers array in function and operator calls.  just have all
	the input vector stored continuously, consequent items at fixed offsets
	appart (min(sizeof double, sizeof long, sizeof pointer) or something)

    have some text _description_ field in function definition

    record variable associated value address (the _state_) with the variable

    eliminate _context_ argument to functions implementing operators

    eliminate the global context to functions implementing functions (and keep
	only the function specific context)

    consolidate _type_ and _load_ atom attributes

-------------------------------------------------------------------------------

ideas:

    references returning functions - the return values would make left values
	cute, but questionable useful
    _object_ returning _aime_ functions
    allow _void_ for _list_ et al item data type
	cute, but questionable useful
    keep the c1 nodes in an array (as opposed to a linked list)

aime3:

    xalist pick and slip
    study allocating l2 list/line/rate objects together with their lx
	controller objects
