Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!uw-beaver!zephyr.ens.tek.com!tekchips!tekgvs!toma
From: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Newsgroups: comp.lang.lisp.x
Subject: Re: xlisp 2.1/winterp internals (26K long)
Message-ID: <8444@tekgvs.LABS.TEK.COM>
Date: 17 Nov 90 17:47:38 GMT
References: <JSP.90Nov15145624@glia.u.washington.edu> <8440@tekgvs.LABS.TEK.COM>
Reply-To: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Distribution: comp
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 22

I hate to followup to my own posting, but:

1. I appologise for all the CR characters at the end of each line.
2. I realized I made a mistake. 
The original posting:
>>xlapply, xlevform and sendmsg will issue an error if they encounter a
>>s_macro CLOSURE.  This is presumably because all macros are expanded
>>by xleval.c:xlclose when it builds a closure.

>>Neither xlapply nor sendmsg will handle FSUBRs.  This is presumably
>>a minor bug, left due to the difficulty of keeping arguments
>>unevaluated to that point. ?

Corrected reply:
Common Lisp does not allow APPLYing a macro or special form (FSUBR).
This is based on the evaluation model.
Since SEND is a subr, all of its arguments are already evaluated so it
is already too late to have macro or fsubr methods.

Tom Almy
toma@tekgvs.labs.tek.com
Standard Disclaimers Apply