6 May
2004
6 May
'04
10:16 p.m.
Helmut Eller <e9626484@stud3.tuwien.ac.at> writes:
Barry Fishman <barry_fishman@att.net> writes:
* (let ((*print-readably* t)) (prin1 '#'+)) #'|COMMON-LISP|::|+| #'+ [snip] Has nobody else seen these problems?
I don't see this with CLISP 2.33 or 2.32. What version are you using? It would be a pity to change *print-readably* to nil, because the current setting detects many errors.
I'm using the current CVS version of CLISP. I have also sent a message to the CLISP developers list asking about the behavior. I agree that setting *print-readably* to nil is a bad thing. -- Barry Fishman