Return to pdae.2 CVS log

Up to [CSRG BSD Unix] / 43BSD / contrib / icon / man / man2

Annotation of 43BSD/contrib/icon/man/man2/pdae.2, revision 1.1.1.1

1.1       root        1: .so tmac.ilib
                      2: .TH PDAE 2 "The University of Arizona \- 8/16/84"
                      3: .SH NAME
                      4: pdae \- programmer-defined argument evaluation
                      5: .SH DESCRIPTION
                      6: These procedures are taken mainly from TR 82-16, which describes
                      7: how co-expressions can be used to model the built-in argument
                      8: evaluation regime of Icon and also provide new ones. Some procedures have
                      9: been corrected or improved.
                     10: .SH SYNOPSIS
                     11: .nf
                     12: .ta 2.0i
                     13: \*MAllpar\^{e1,\*be2,\*b \*(El}\fR     parallel evaluation with last result used for short sequences
                     14: \*MCall(a)\fR  utility procedure to call functions
                     15: \*MExtract\^{e1,\*be2, \*(El}\fR       extract results of even-numbered arguments according to
                     16:           odd-numbered values
                     17: \*MLifo\^{e1,\*be2, \*(El}\fR  models standard Icon `lifo' evaluation
                     18: \*MParallel\^{e1,\*be2, \*(El}\fR      parallel evaluation terminating on shortest sequence
                     19: \*MReverse\^{e1,\*be2, \*(El}\fR       left-to-right reversal of lifo evaluation
                     20: \*MRotate\^{e1,\*be2, \*(El}\fR        parallel evaluation with shorter sequences re-evaluated
                     21: \*MSimple\^{e1,\*be2, \*(El}\fR        simple evaluation with only success or failure
                     22: .SH REQUIREMENTS
                     23: \fIPdae\fR requires the experimental extensions in Version 5.9 of Icon.
                     24: .SH BUGS AND LIMITATIONS
                     25: Because of the handling of the scope of local identifiers in co-expressions,
                     26: expressions in programmer-defined argument evaluation regimes cannot communicate
                     27: through local identifiers. The results produced by programmer-defined
                     28: argument evaluation regimes are always dereferenced. Some constructions, such
                     29: as \*Mbreak\fR and \*Mreturn\fR, cannot be used in arguments to programmer-defined
                     30: argument evaluation regimes. See TR 82-8 for details of these problems.
                     31: .PP
                     32: At most 10 arguments can be used in the invocation of a programmer-defined
                     33: argument evaluation regime. This limit can be increased by
                     34: modifying \*MCall\fR.
                     35: .SH SEE ALSO
                     36: pdco(2)
                     37: .PP
                     38: .Pd
                     39: .PP
                     40: Novak, Michael and Ralph E. Griswold. \fIProgrammer-Defined Argument
                     41: Evaluation Regimes\fR, TR 82-16,
                     42: Department of Computer Science, The University of Arizona, 1982.
                     43: .PP
                     44: .Ex
                     45: .SH AUTHORS
                     46: Ralph E. Griswold and Michael Novak

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.