[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
+INTERNAL-/'-MACRO
- To: GSB at MIT-MC
- Subject: +INTERNAL-/'-MACRO
- From: JONL at MIT-MC (Jon L White)
- Date: Sat, 20 Sep 80 18:41:00 GMT
- Cc: (BUG LISP) at MIT-MC
- Original-date: 20 SEP 1980 1441-EDT
From: GSB@MIT-ML
Date: Fri, 20 Sep 80 02:46:16 GMT
Original-Date: 09/19/80 22:46:16 EDT
Subject: Re: fixing things
It seems that +INTERNAL-/'-MACRO now calls a read entry which calls
the read hook. . . . The read hook has semantics of being a "toplevel"
call and is allowed to do things like flush the character trailing a
character. This isn't right for a recursive read.
It's not entirely clear what the purpose of this read "hook" is -- the
toplevel hook is another feature (READ-*-EVAL-PRINT and *-READ-EVAL-PRINT) --
and furthermore, its not clear that we've resolved the READ-PRESERVE-DELIMITERS
problem for maclisp; but your comment seems right, that READ rather than
(LAMBDA (X) (COND (READ (FUNCALL READ X)) ((READ X))))
is what is desired. So I've again patched it accordingly.