[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Splicing macros
- To: (BUG LISP) at MIT-AI
- Subject: Re: Splicing macros
- From: ALAN@MIT-AI
- Date: Fri, 1 Sep 79 06:49:09 GMT
- Original-date: 01/09/79 02:49:09 EDT
After a dot a splicing macro that returns nil ("nothing") should
cause the next thing to be read in as if it wern't there (this is what the
current scheme thinks it is doing except there is no check for a ")").
If it returns a list of exactly one thing, then that thing should
be tacked on to the end of the list and there better be a close paren next!
(or perhaps a splicing macro that returns nil first!)
If it returns more than one thing then barf.
Is there any good reason why things can't work this way? Shouldn't splicing
macros at toplevel also work in a similar way? In any case an error should
be reported if the thing is going to continue to do what it does now.