[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: printing structures
- To: RWK@YUKON.SCRC.Symbolics.COM
- Subject: Re: printing structures
- From: Masinter.pa@Xerox.COM
- Date: Mon, 06 Oct 1986 00:08:00 -0000
- Cc: common-lisp@SU-AI.ARPA
- In-reply-to: Robert W. Kerns <RWK@YUKON.SCRC.Symbolics.COM>'s message of Sat, 4 Oct 86 21:16 EDT
Separating out I/O for for inter-program communication and the
user-interface is a good idea, but your proposal puts the burden on
inter-program communication ("wrap this one form around the portion of
your program which does I/O.") rather than on the user interface.
Wouldn't it be simpler to suggest that implementors of a
"top-level-loop" might want to bind a separate I/O environment for
reading and printing (but not for execution)?
Back onto the original discussion: we added a variable *print-structure*
which controlled how structures were printed by the default structure
printer, in the same way that *print-array* controls array output. I'm
reluctant to propose additions to the language, but if one was wanted,
this seems like a logical choice.