[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: multiple-valued macros (was: do-nothing macro generates nil nevertheless)
- To: firstname.lastname@example.org
- Subject: Re: multiple-valued macros (was: do-nothing macro generates nil nevertheless)
- From: email@example.com (Darius Bacon)
- Date: 25 Mar 1995 23:32:36 GMT
- Organization: The Whole Earth 'Lectronic Link, Sausalito, CA
- References: <firstname.lastname@example.org>, <email@example.com>, <19950227T181439Z.firstname.lastname@example.org>
- Sender: email@example.com
firstname.lastname@example.org (Erik Naggum) writes:
>multiple-valued macros would certainly pose interesting problems in parsing
>and evaluation. for completeness, we should also consider multiple-valued
>reader-macroes. the mind boggles.
According to the first edition of _AI Programming_, UCI Lisp had 'splicing'
read macros -- they returned a list that got spliced into the input stream.
I think the justification was that they wanted to handle comments with a
read macro, but they didn't have proper tail recursion and it had to run on
machines with tiny memories.