[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Readtables and prin1
- To: Scott E. Fahlman <Fahlman@CMU-CS-C.ARPA>
- Subject: Re: Readtables and prin1
- From: Brad Miller <miller@UR-ACORN.ARPA>
- Date: Thu, 18 Sep 86 10:00 EDT
- Cc: common-lisp@SU-AI.ARPA
- Fcc: ACORN:>miller>babyl.text
- In-reply-to: <FAHLMAN.12239777784.BABYL@C.CS.CMU.EDU>
- Moon: 7 minutes since the full moon.
- Organization: University of Rochester, Department of Computer Science
- Phone: 716-275-7747
- Postal-address: 617 Hylan Building, University of Rochester, Rochester NY 14627
- Sender: miller@UR-ACORN.ARPA
Date: Wed, 17 Sep 1986 21:07 EDT
From: "Scott E. Fahlman" <Fahlman@C.CS.CMU.EDU>
I think that the usual practice is to print things out so that they can
be read in using the standard readtable. It would be VERY difficult to
write code that can print out text for any user-modified readtable,
especially if the read-table contains macros.
It may be hard, but I suspect necessary. Given the user is in some context, he
would expect his print function to work "so it can be read in again" which
implies in his current context. Having to change contexts just to enter forms
(which would then get into even more difficult problems about packaging, etc.
in the new context) is not in my opinion a good user interface.