[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

#\STOP-OUTPUT ;continued

No. Nested #+'s are bad enuf. Bug telling a guy that inside a 
#+LISPM he may need do do some #-LISPM conditionals? That's far
from intuitive.

Also, for Sussman's sake (and I think he takes a reasonable position),
whatever we decide to do must work inside of (IF-FOR-LISPM ...). It
cannot be constrained to work only inside of #+LISPM or #Q. That would
be very ugly.

Finally, we do want to allow the #\... things which are invalid to 
compose structure, otherwise they will be very hard to debug. It is easy
for someone to recognize bad structure once it is read in, but read
errors are the bane of lisp programming because they do not give you a
hold on your program -- you cannot look at them in debuggers, etc. This
is why Bob and I decided that even in the erring case, we need to cons
a form successfully during READ (even if such a form will err at EVAL).