[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
#+LISPM on ITS
- To: (BUG LISP) at MIT-MC
- Subject: #+LISPM on ITS
- From: KMP at MIT-MC (Kent M. Pitman)
- Date: Sun ,3 Feb 80 21:44:00 EDT
CC: (BUG LISPM) at MIT-MC
This bothers me:
On ITS, #+LISPM <form> causes all the symbols in <form> to get INTERN'd even
on ITS because the real reader is called.
Less annoying, but an artifact of the same problem, is that
#+LISPM #.(PRINT 'FOO) will print FOO even on ITS. Must I really do
#. #+LISPM (PRINT 'FOO) #-LISPM ()
in order to win? I wonder if we shouldn't look into making the reader
recognize it's in a no-op state to suppress #. and INTERN and some of these
other things from really doing their thing. I don't want to do this in a
hackish way so am looking for suggestions for reasonable schemes. The main
intention being that I don't have to do a huge GCTWA when all done reading
some conditionalized file.
-kmp