Re: New draft (#3) and last call for comments on SRFI 197: Pipeline Operators Marc Nieper-Wißkirchen (31 Aug 2020 17:42 UTC)
multiple-values and chain-and Dr. Arne Babenhauserheide (24 Aug 2020 11:51 UTC)
Re: multiple-values and chain-and Marc Nieper-Wißkirchen (24 Aug 2020 12:02 UTC)
Re: multiple-values and chain-and Dr. Arne Babenhauserheide (24 Aug 2020 14:03 UTC)
Re: multiple-values and chain-and Marc Nieper-Wißkirchen (24 Aug 2020 14:13 UTC)
Re: multiple-values and chain-and Dr. Arne Babenhauserheide (29 Aug 2020 11:38 UTC)
Re: multiple-values and chain-and Adam Nelson (28 Aug 2020 02:47 UTC)

Re: New draft (#3) and last call for comments on SRFI 197: Pipeline Operators Marc Nieper-Wißkirchen 31 Aug 2020 17:42 UTC

Am Mo., 31. Aug. 2020 um 19:03 Uhr schrieb Adam Nelson <xxxxxx@nels.onl>:

> I'm not sure what the correct term is when referring to a list form that could be either a procedure call, macro call, or special form. Perhaps "application" is the most general term? Or "list form"?

Your macro just does textual substitution, which is uncommon for the
usual derived forms/standard macro. So this may be the reason why
there is no established name.

You could write:

****

(nest <step> ... <initial datum>)

Syntax: <step> has the syntax (<datum> ... _ <datum> ...) and <initial
datum> can be any datum.

Semantics: A nest expression is evaluated by lexically replacing the
underscore in the last <step> with <initial datum> and then replacing
the underscore is the next to last <step> by that replacement and so
on until the underscore in the first <step> has been replaced. It is
an error if the resulting final replacement is not an expression,
which is then evaluated and its values are returned.

****