[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Sandra J Loosemore <email@example.com>
- Subject: Re: COMPILER-LET
- From: firstname.lastname@example.org
- Date: Tue, 27 Sep 88 10:27:47 -0700
- Cc: email@example.com, firstname.lastname@example.org, email@example.com
- In-reply-to: Your message of Mon, 26 Sep 88 13:36:01 -0600. <8809261936.AA05384@defun.utah.edu>
I want to reply to your comments that COMPILER-LET is (1) ugly and confusing,
(2) rarely used, and (3) can be replaced with MACRO-LET. The second point is
probably true. As to the other points I wish to disagree. As to the first
point: I was delighted to see COMPILER-LET in the language because it was the
obvious clean LISPish way to gain a lot of useful capability for compilers and
extentions layered on top of LISP.
The method that you showed of using MACRO-LET doesn't really work very well.
There is a strategy that will work but it is a real croc: A macro that was
going to output the COMPILER-LET wrapper outputs a MACRO-LET that includes a
local macro that produces the quoted of the value that would have been bound to
the special variable. A macro that wishes to consume that value must pass a
form like (LOCAL-MACRO-NAME) to EVAL along with an environment pointer.
- From: firstname.lastname@example.org (Sandra J Loosemore)