|
ABSTRACT
The maintenance of arbitrarily large tables of previously computed values for functions on integer domains becomes practical when those tables are built using constructor functions which suspend evaluation of their arguments. Two styles of programming with such tables are presented. The first results from replacing recursive invocations within standard recursive function definitions with a reference into a table which is predefined to be all the possible results of the function. The second, more sophisticated, style requires that the table be defined strictly through a generation scheme. In either case the table may be available to the user as a data structure exclusive of the function definition with entries still being manifested only when they are actually used.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
1
|
G. Berry. Bottom-up computation of recursive programs. Revue Francaise d'Informatique et de Recherche Operationaelle 10, 3 (March, 1976), 47-82.
|
| |
2
|
W.H. Burge. Recursive Programming Techniques, Addison-Wesley, Reading, MA (1975).
|
| |
3
|
D.P. Friedman and D.S. Wise. Cons should not evaluate its arguments. Third International Colloquium on Automata, Languages and Programming, Edinburgh University Press (July, 1976).
|
 |
4
|
|
| |
5
|
C.A.R. Hoare. Recursive data structures. International Journal of Computer and Information Sciences 2, (June, 1975), 105-132.
|
 |
6
|
|
|